I've seen folks get a misconfigure like this when they make the call
in the application's constructor instead of the init() method.

On Friday, April 29, 2011, Martin Grigorov <mgrigo...@apache.org> wrote:
> Hi,
> On Thu, Apr 28, 2011 at 9:50 PM, Alec Swan <alecs...@gmail.com> wrote:
>> Thanks, Andrea. I was running in DEVELOPMENT mode and switching to
>> DEPLOYMENT mode fixed the problem. I hope this gets documented
>> somewhere.
> You are doing something wrong. MyApp#init() is called after
> WebApplication#internalInit() so your settings should override the
> defaults.

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to