Technically this is not a bug. If you're happy with the default
constructor of the super class Java will call it for you if you don't
call it explicitly.
So this is more a question of style. I personally usually call super
to be explicit.
On 31/01/2009, at 5:23 AM, Kieran Kelleher (JIRA) wrote:
> Wonder Application template project's Application class constructor
> does not call super()
> -----------------------------------------------------------------------------------------
>
> Key: WOL-965
> URL: http://issues.objectstyle.org/jira/browse/WOL-965
> Project: WOProject/WOLips
> Issue Type: Bug
> Environment: WOLips 3.4.5667 Nightly
> Reporter: Kieran Kelleher
>
>
> The Application class in a new Wonder Application project does not
> call super() in its constructor:
>
> public Application() {
> ERXApplication.log.info("Welcome to " + name() + " !");
> /* ** put your initialization code in here ** */
> }
>
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> administrators: http://issues.objectstyle.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
with regards,
--Lachlan Deck
This archive was generated by hypermail 2.0.0 : Fri Jan 30 2009 - 20:34:52 EST