[
https://issues.apache.org/jira/browse/GERONIMO-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787220#comment-13787220
]
Arjan Tijms commented on GERONIMO-6492:
---------------------------------------
Unfortunately, it seems to have an effect after all.
{{@Named}} beans from war1 are available in war2 using their EL name (this
should not be of course!), and {{@Named}} beans from war2 are unavailable in
war2.
Meaning, that e.g. EL expressions using {{@Named}} beans (or using their
default name) don't work in war2. However, CDI itself is definitely available
in war2 as direct injection of CDI managed beans that only exist in war2 does
work.
> Duplicate war message if EAR with two wars both contain beans.xml
> -----------------------------------------------------------------
>
> Key: GERONIMO-6492
> URL: https://issues.apache.org/jira/browse/GERONIMO-6492
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 3.0.1
> Reporter: Arjan Tijms
>
> Using a trivial EAR with two web modules inside it, both being nearly empty
> except for a single .jsp page and an empty {{beans.xml}} in {{WEB-INF}}
> causes a message about a duplicate war to be logged:
> {noformat}
> 2013-10-02 11:30:21,499 WARN [AdminObjectRefBuilder] Failed to build
> reference to resource env reference [java:comp/BeanManager] defined in plan
> file. The corresponding entry in Geronimo deployment descriptor is missing.
> 2013-10-02 11:30:21,551 WARN [EjbModuleBuilder] Duplicated moduleName:
> 'omtest2' is found ! deployer will rename it to: 'omtest2_duplicated' ,
> please check your modules in application to make sure they don't share the
> same name
> 2013-10-02 11:30:21,552 WARN [AdminObjectRefBuilder] Failed to build
> reference to resource env reference [java:comp/BeanManager] defined in plan
> file. The corresponding entry in Geronimo deployment descriptor is missing.
> {noformat}
> The EAR is structured as follows:
> {noformat}
> omtest.ear
> omtest1.war
> WEB-INF
> beans.xml
> index.jsp
> omtest2.war
> WEB-INF
> beans.xml
> index.jsp
> {noformat}
> Optionally adding deployment descriptors {{application.xml}} and
> {{geronimo-application.xml}} to list the modules and set the context root of
> each war does not solve the problem.
> The message disappears as soon as {{beans.xml}} in the second war is removed.
> At first sight the code seems to be deployed fine, as the {{index.jsp}} files
> in both wars are accessible via their respective URLs.
> Yet, this may be indicative of a deeper problem with CDI in a multi-war EAR
> application.
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
