[jira] [Updated] (WICKET-6441) MockSessionStore doesn't call onInvalidate() on invalidate()

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov updated WICKET-6441:
------------------------------------
    Summary: MockSessionStore doesn't call onInvalidate() on invalidate()  (was: MockHttpSession doesn't call onInvalidate() on invalidate())

> MockSessionStore doesn't call onInvalidate() on invalidate()
> ------------------------------------------------------------
>
>                 Key: WICKET-6441
>                 URL: https://issues.apache.org/jira/browse/WICKET-6441
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 8.0.0-M6
>            Reporter: Kamil
>             Fix For: 8.0.0, 7.10.0
>
>         Attachments: showcase-onInvalidate.zip
>
>
> org.apache.wicket.protocol.http.mock.MockHttpSession on invalidate calls just:
> {code}
> @Override
> public void invalidate()
> {
> 	attributes.clear();
> 	id = generateSessionId();
> }
> {code}
> while org.apache.wicket.session.HttpSessionStore valueUnbound calls
> {code}
> public void valueUnbound(final HttpSessionBindingEvent evt)
> {
> 	String sessionId = evt.getSession().getId();
> 	log.debug("Session unbound: {}", sessionId);
> 	if (wicketSession != null)
> 	{
> 		wicketSession.onInvalidate();
> 	}
> ...
> }
> {code}
> (valueUnbound is called on org.apache.catalina.session.StandardSession.invalidate)
> this causes to be impossible to properly test what happens on invalidation of the session.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)