[weld-issues] [JBoss JIRA] Closed: (WELD-675) Add a ServletContext configuration parameter for enabling/disabling automatic session creation in WeldListener/ServletLifecycle

[Pete Muir (JIRA)]

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

Pete Muir closed WELD-675.
--------------------------

         Assignee: Pete Muir
    Fix Version/s:     (was: 1.1.0.Beta2)
       Resolution: Won't Fix


Closing, as this is easily resolved by upgrading to Jetty 6.1.17 or newer

> Add a ServletContext configuration parameter for enabling/disabling automatic session creation in WeldListener/ServletLifecycle
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WELD-675
>                 URL: https://jira.jboss.org/browse/WELD-675
>             Project: Weld
>          Issue Type: Feature Request
>          Components: Servlet Container Support
>    Affects Versions: 1.1.0.Beta1
>            Reporter: Marius Bogoevici
>            Assignee: Pete Muir
>
> As noted by Heiko here:
> http://github.com/weld/core/pull/10
> , the ServletListener  breaks in some versions of Jetty, since getSession() is unable to create a new Session.
> However, completely disabling new session creation for the listener changes the way ServletListener behaves, in that the first request hitting a newly started server may not have a sessioncontext/requestcontext/conversationcontext assigned to it. 
> While this can work fine in general, I think that we need some ability to finely tune this, by adding a ServletContext parameter which would control this behaviour (allow new session creation by default, but allow users to turn this off)

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