[
https://jira.jboss.org/browse/JBAS-8472?page=com.atlassian.jira.plugin.sy...
]
Marius Bogoevici commented on JBAS-8472:
----------------------------------------
Actually, the solution is to avoid propagating the whole set to EjbDescriptors to every BM
in the deployment. Rather, the BMs should create beans only for the EJBs that they deploy.
Afterwards, EJBs will be accessible via the 'transitive beans' mechanism.
EAR deployments that contain EJBs fail because of bean duplication
------------------------------------------------------------------
Key: JBAS-8472
URL:
https://jira.jboss.org/browse/JBAS-8472
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Affects Versions: 6.0.0.M5
Reporter: Marius Bogoevici
Assignee: Marius Bogoevici
Fix For: 6.0.0.CR1
The problem is that the EAR level BM and module-level BM contain a copy of
EjbContainerServices which results in the bean being present twice (in different BMs but
hierarchically related).
Solution proposal: register an empty EjbContainerService for modules and delegate EJB
resolution to the top-level BM - in EARs.
--
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