[weld-issues] [JBoss JIRA] (WELD-731) Bind BeanManager to JNDI when naming context is read/write (as in JBoss AS/EAP 5)

[Jozef Hartinger (JIRA)]

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

Jozef Hartinger updated WELD-731:
---------------------------------

    Fix Version/s: 2.0.0.Alpha2

    
> Bind BeanManager to JNDI when naming context is read/write (as in JBoss AS/EAP 5)
> ---------------------------------------------------------------------------------
>
>                 Key: WELD-731
>                 URL: https://issues.jboss.org/browse/WELD-731
>             Project: Weld
>          Issue Type: Feature Request
>          Components: Servlet Container Support
>    Affects Versions: 1.1.0.Beta1
>            Reporter: Dan Allen
>            Assignee: Christian Sadilek
>             Fix For: 1.2.0.Beta1, 2.0.0.Alpha2
>
>         Attachments: BeanManagerResourceBindingListener.java
>
>
> It's possible for the Weld servlet listener to be proactive and bind the BeanManager to JNDI when the naming context is read/write, as it is in JBoss AS and EAP 5. There's another good reason why this needs to be done. JBoss AS does not support defining naming resources in context.xml (which on JBoss AS is WEB-INF/context.xml). Therefore, there's no other way to push the BeanManager into JNDI.
> The logic for this feature is pretty straightforward. Look for the BeanManager in JNDI. If it's not there, attempt to put it there. If that fails, just log a warning message that the BeanManager will not be available in JNDI.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira