Hi, The question is what leads to the call of Session#bind(). While the debugger is at Session#bind() see what is the stacktrace from top to bottom. Maybe after logout you redirect to a stateful page and Wicket needs to create a new Session to store that page ...
On Thu, Feb 21, 2019 at 10:21 AM kyc <[email protected]> wrote: > As I encountered the same problem as AliKhan, I follow Martin's suggestion > to upgrade the wicket version from 7.10 to 7.12. However, I still go to > the > following code inside the bind() method when the session is invalidate. > > // explicitly create a session > id = store.getSessionId(request, true); > // bind it > store.bind(request, this); > > > Session.java > public final void bind() > { > // If there is no request cycle then this is not a normal > request but for > example a last > // modified call. > if (RequestCycle.get() == null) > { > return; > } > > ISessionStore store = getSessionStore(); > Request request = RequestCycle.get().getRequest(); > if (store.lookup(request) == null) > { > // explicitly create a session > id = store.getSessionId(request, true); > // bind it > store.bind(request, this); > > if (temporarySessionAttributes != null) > { > for (Map.Entry<String, Serializable> entry > : > temporarySessionAttributes.entrySet()) > { > store.setAttribute(request, > entry.getKey(), entry.getValue()); > } > temporarySessionAttributes = null; > } > } > } > > -- > Sent from: > http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
