I think we have to improve Application#setPageMangerProvider():

public synchronized final void setPageManagerProvider(final IPageManagerProvider provider)
    {
        pageManagerProvider = provider;

        if (pageManager != null)
        {
            synchronized (this)
            {
                if (pageManager == null)
                {
                    pageManager.destroy();
                    pageManager = null;
                }
            }
        }
    }

WDYT?

Sven

On 10/25/2013 12:14 AM, uwe schaefer wrote:
On 22.10.2013 10:22, Sven Meier wrote:

Hi Sven,

currently there's no way to change the PageManager once it's fetched in
Application#internalGetPageManager().

agreed.

Do you have a stacktrace for the code triggering
Application.getPageManagerProvider().get() ? Besides devutils I don't
see any call to this from Wicket.

it is the sessionUnbound method that supposedly was triggered by the container doing its clustering while wicket still initializes;

Application:478
public void sessionUnbound(final String sessionId){
  internalGetPageManager().sessionExpired(sessionId);
  ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
}

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

Reply via email to