Hi Henry,
You have two solutions and nothing else:
1) Override the method getConfigurationType() in your application class
2) Add in your web.xml:
<context-param>
<param-name>wicket.configuration</param-name>
<param-value>deployment</param-value>
</context-param>
or in your filter:
@WebInitParam(name="wicket.configuration", value="deployment")
I also work with glassfish and it's ok for me.
2011/5/4 henry <henstri...@yahoo.com>
> Hi Moez,
>
> Could it be a result of the wicket version that am using?Because i have
> cleared web container and i still get same message.Take a look at this.
>
>
> [Application] Started Wicket version 1.4-rc1 in development mode
> ********************************************************************
> *** WARNING: Wicket is running in DEVELOPMENT mode. ***
> *** ^^^^^^^^^^^ ***
> *** Do NOT deploy to your live server(s) without changing this. ***
> *** See Application#getConfigurationType() for more information. ***
>
> Application started with version 1.4-rc1 in development mode.Dont seems to
> understand that,is is that by default wicket runs its application in a
> development mode?
>
> please need more help on this.
>
> Regards............
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/moving-from-development-to-deployment-mode-tp3495199p3495527.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
