[jboss-jira] [JBoss JIRA] Updated: (JBAS-8170) Make the BeanManager available in JNDI under a unique name for each deployment

[Jason T. Greene (JIRA)]

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

Jason T. Greene updated JBAS-8170:
----------------------------------

    Fix Version/s: TBD-6.x
                       (was: 6.0.0.M4)


All uncompleted issues are now moved to the new "To be determined for future 6.x releases" category. Feel free to reassign this to a specific release, but only if you have the time to do it

> Make the BeanManager available in JNDI under a unique name for each deployment
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-8170
>                 URL: https://jira.jboss.org/browse/JBAS-8170
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Weld/CDI
>    Affects Versions: 6.0.0.M3
>            Reporter: Marius Bogoevici
>            Assignee: Marius Bogoevici
>             Fix For: TBD-6.x
>
>
> As required by the Java EE specification, the BeanManager for a CDI-enabled Java EE component or module must be available under java:comp/BeanManager. As an extension to that, the BeanManager for a given deployment should also be available under a unique deployment-unit specific name.

-- 
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