[jboss-jira] [JBoss JIRA] Commented: (JBAS-8939) Expose BeanManager in JNDI even for non Java EE module deployments

[Tom Fennelly (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587346#comment-12587346 ] 

Tom Fennelly commented on JBAS-8939:
------------------------------------

Marius, one obvious thing that comes to mind about this solution is that it will mean that anything that relies on this new feature will not be able to run on earlier versions of AS6, right?  In the case of SwitchYard, that's probably going to be an issue (need to check that).

I might have a look ar the current Weld war deployer + JndiBinder class and see can we replicate that for SwitchYard.  If it works, can we make sure that the resolution of this issue checks that the BeanManger is not already bound in. 

> Expose BeanManager in JNDI even for non Java EE module deployments
> ------------------------------------------------------------------
>
>                 Key: JBAS-8939
>                 URL: https://issues.jboss.org/browse/JBAS-8939
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 6.0.0.Final
>            Reporter: Marius Bogoevici
>            Assignee: Marius Bogoevici
>             Fix For: 6.1.0
>
>
> Currently the Weld deployer registers the BeanManager in JNDI in the global namespace if the deployment is a WAR or EJB-JAR. 
> Expose the Weld deployer in the global namespace even if the deployment is not a WAR or EJB-JAR. This is necessary for non-Java EE deployments (e.g. an ESB jar).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira