[JBoss JIRA] Created: (JBAS-8939) Expose BeanManager in JNDI even for non Java EE module deployments
6:39 p.m.
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
2:40 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8939) Expose BeanManager in JNDI even for non Java EE module deployments
[
https://issues.jboss.org/browse/JBAS-8939?page=com.atlassian.jira.plugin....
]
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
2:39 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-8939) Expose BeanManager in JNDI even for non Java EE module deployments
[
https://issues.jboss.org/browse/JBAS-8939?page=com.atlassian.jira.plugin....
]
Shelly McGowan updated JBAS-8939:
---------------------------------
Fix Version/s: (was: 6.1.0)
Expose BeanManager in JNDI even for non Java EE module deployments
------------------------------------------------------------------
Key: JBAS-8939
URL: https://issues.jboss.org/browse/JBAS-8939
Project: Legacy JBoss Application Server 6
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.Final
Reporter: Marius Bogoevici
Assignee: Marius Bogoevici
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
4910
days inactive
5054
days old
2 comments
3 participants
participants (3)
-
Marius Bogoevici (JIRA) -
Shelly McGowan (JIRA)
-
Tom Fennelly (JIRA)