Hi Uwe,
currently there's no way to change the PageManager once it's fetched in
Application#internalGetPageManager().
Do you have a stacktrace for the code triggering
Application.getPageManagerProvider().get() ? Besides devutils I don't
see any call to this from Wicket.
Regards
Sven
On 10/21/2013 06:16 PM, uwe schaefer wrote:
On 10/21/2013 09:07 AM, Martin Grigorov wrote:
Hi Martin,
I hope the ticket will describe better what "and the damage is done"
actually means.
sorry if i was unclear. looks like i got lost in the details.
the actual damage is: there is a Thread started and associated with a
AsynchronousDataStore, which is not used and superseeded during init()
with the HttpSession-based DataStore to be actually used.
There is no obvious way to get a reference to that thread, so that it
cannot be stopped on destruction of the application - thus
redeployment gets problematic.
cu uwe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
