[
https://issues.jboss.org/browse/JBSEAM-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jozef Hartinger closed JBSEAM-4787.
-----------------------------------
Assignee: Jozef Hartinger
Fix Version/s: 2.3.0.ALPHA
Resolution: Duplicate Issue
This regression has already been fixed in JBSEAM-4775
> Session is destroyed by RESTeasy call
> -------------------------------------
>
> Key: JBSEAM-4787
> URL: https://issues.jboss.org/browse/JBSEAM-4787
> Project: Seam
> Issue Type: Bug
> Affects Versions: 2.2.1.Final
> Environment: JBoss 5.1.0 GA jdk 6, Windows Vista, Chrome and FF 3.6
> Reporter: Ernst-Jan van der Laan
> Assignee: Jozef Hartinger
> Fix For: 2.3.0.ALPHA
>
>
> Due to the fix for JBSEAM-4770 sessions are always removed, with the setting
> <resteasy:application destroy-session-after-request="true" /> (which is the
> default). This is a problem when the session actualy existed, and is not
> created, because the complete conversation is destroyed.
> ContextualHttpServletRequest.java: line 44
> // Force creation of the session
> if (request.getSession(false) == null)
> {
> request.getSession(true);
> }
> ResteasyResourceAdapter.java: line 149
> // Prevent anemic sessions clog up the server
> if (application.isDestroySessionAfterRequest())
> {
> log.debug("Destroying HttpSession after REST request");
> Session.instance().invalidate();
> }
> What actualy should happen is that the session is not destroyed when it
> already existed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
