[
https://issues.apache.org/jira/browse/IGNITE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179646#comment-15179646
]
Roman Shtykh edited comment on IGNITE-2710 at 3/4/16 9:55 AM:
--------------------------------------------------------------
Anton,
I changed the implementation by storing a genuine session, as you advised.
Looks nice and simple to me.
_isValid_'s use becomes trivial -- just to follow specifications and produce
_IllegalStateException_ when invalid.
was (Author: roman_s):
Anton,
I changed the implementation by storing a genuine session, as you advised.
_isValid_'s use becomes trivial -- just to follow specifications and produce
_IllegalStateException_ when invalid.
> Session not unbind from current request after invoking
> request.getSession().invalidate()
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-2710
> URL: https://issues.apache.org/jira/browse/IGNITE-2710
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5.0.final
> Environment: java8, tomcat8
> Reporter: YuxuanWang
> Assignee: Roman Shtykh
> Labels: community, session, user
> Fix For: 1.6
>
>
> System.out.println(request.getSession().getId());
> request.getSession().invalidate();
> System.out.println(request.getSession().getId());
> getSession() although return the same session after the invalidation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
