ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yucigou <yuci....@gmail.com>
Subject Re: It seems WebSession's removeAttribute does not support HttpSessionBindingListener
Date Wed, 05 Jul 2017 10:25:26 GMT
Ignite WebSessionV2 uses genuineSes as the original HttpSession.

Therefore, when setting an attribute or setting the maxInactiveInterval,
Ignite should tell the original HttpSession about it.

Otherwise, when the web container (such as Tomcat) thinks that a session
expires, or is invalidated, or a session attribute gets removed, etc.,
session attributes' HttpSessionBindingListener's valueUnbound callback
function will not get fired.

So once the original HttpSession gets updated with the session attributes
and the maxInactiveInterval, the web container will transitively trigger the
session attributes' HttpSessionBindingListener's valueUnbound callback
function when a session expires, etc.

(By the way, tested with our app, and our issue is fixed:

View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/It-seems-WebSession-s-removeAttribute-does-not-support-HttpSessionBindingListener-tp19184p19480.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

View raw message