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

[Dan Allen (JIRA)]

    [ https://jira.jboss.org/browse/WELD-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557457#action_12557457 ] 

Dan Allen commented on WELD-731:
--------------------------------

I should mention that this functionality is a key piece for allowing Arquillian to be able to test CDI on JBoss AS and EAP 5 (without extra configuration on the developer's part).

> Bind BeanManager to JNDI when naming context is read/write (as in JBoss AS/EAP 5)
> ---------------------------------------------------------------------------------
>
>                 Key: WELD-731
>                 URL: https://jira.jboss.org/browse/WELD-731
>             Project: Weld
>          Issue Type: Feature Request
>          Components: Servlet Container Support
>    Affects Versions: 1.1.0.Beta1
>            Reporter: Dan Allen
>             Fix For: 1.1.0.CR1
>
>         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 contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira