If i recall correctly from way way back when wicket was still version 1.2.x :) there is no guarantee that session.detach will be called for every session.attach due to some synchronized thingies :)
We are talking wicket 1.2 here so this might not be relevant in this situation (any more) but i believe there were reasons not to synchronize the complete request, performance being one of them. Maurice On 9/25/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > In my current project well fell over this looking at: > > > > WicketFilter.getLastModified(final HttpServletRequest servletRequest) > > where cachable resources lead over Session.findOrCreate to > > Session.set(Session) to Session.attach() > > > > but the Session.unset() doesn't lead to a Session.detach() > > Sounds wrong to me. Would you mind opening a JIRA issue for that please? > > Eelco >
