[weld-issues] [JBoss JIRA] Assigned: (WELD-403) Activate session scope after call to HttpSession.invalidate()

[David Allen (JIRA)]

     [ https://jira.jboss.org/jira/browse/WELD-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Allen reassigned WELD-403:
--------------------------------

    Assignee: David Allen


> Activate session scope after call to HttpSession.invalidate()
> -------------------------------------------------------------
>
>                 Key: WELD-403
>                 URL: https://jira.jboss.org/jira/browse/WELD-403
>             Project: Weld
>          Issue Type: Feature Request
>          Components: Scopes & Contexts
>    Affects Versions: 1.0.0.GA
>            Reporter: steven verborgh
>            Assignee: David Allen
>             Fix For: 1.0.1.CR1
>
>         Attachments: session_invalidate.tar.bz2
>
>
> When calling HttpSession.invalidate() and redirecting to a page that uses a SessionScoped Bean a ContextNotActiveException exception gets thrown.
> This is a different behavior than when using the optional JSF annotations (ManagedBean, SessionScoped) and is also different from the standard HttpRequest behaviour where a call HttpRequest.getSession() by default creates a new Session, even after a call to invalidate in the same request/response cycle.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira