On Tue, Oct 11, 2011 at 12:58 AM, Chris Colman
chr...@stepaheadsoftware.com wrote:
I have a workaround that's probably a bit of a hack but it works ;)
Yep, we are aware that IInitializers override Application's
configuration: https://issues.apache.org/jira/browse/WICKET-4088
I just removed the autoregistering of DebugDiskDataStore when
wicket-devutils is enabled:
https://issues.apache.org/jira/browse/WICKET-4120.
Now if someone wants to browse the disk store she will have to
register it manually in her Application#init().
I overwrite Application#validateInit() and set it there:
protected void validateInit()
{
super.validateInit();
setPageManagerProvider(new MyPageManagerProvider());
}
From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
Sent: Tuesday, 11 October 2011 8:24 AM
To: users@wicket.apache.org
Subject: Settting of PageManagerProvider is overridden in debug mode
In debug mode, setting the page manager provider like this:
setPageManagerProvider(new MyPageManagerProvider(this));
in MyApplication#init()
gets overridden because after the derived class init() is called
Application executes some debug behaviour if in debug mode. This
behaviour always sets the PageManagerProvider to the
DebugPageManagerProvider, overriding any setting made in the derived
class' init() method. I need a custom PageManagerProvider in both debug
and production modes.
Is there any way around this?
Yours sincerely,
Chris Colman
Pagebloom Team Leader,
Step Ahead Software
pagebloom - your business your website growing together
Sydney: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120
Email: chr...@stepahead.com.au mailto://chr...@stepahead.com.au
Website:
http://www.pagebloom.com blocked::http://www.pagebloom.com/
http://develop.stepaheadsoftware.com
blocked::http://develop.stepaheadsoftware.com/
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org