[jboss-jira] [JBoss JIRA] (WFLY-3419) beans in module jars are not discovered except the first jar in module

[Petr Sakař (JIRA)]

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

Petr Sakař commented on WFLY-3419:
----------------------------------

[~jason.greene] EAP currently behaves as expected - beans are discovered only in jar with beans.xml. I would suggest to keep the restriction, as it gives precise control which jar in module should be scanned. The problem in Wildfly is that only first jar including beans.xml is scanned, others containing beans.xml are not scanned.

> beans in module jars are not discovered except the first jar in module
> ----------------------------------------------------------------------
>
>                 Key: WFLY-3419
>                 URL: https://issues.jboss.org/browse/WFLY-3419
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: CDI / Weld
>    Affects Versions: 8.0.0.Final, 8.1.0.Final
>            Reporter: Petr Sakař
>            Assignee: Jason Greene
>         Attachments: jboss-module-test.src.zip, module.multiplejars.zip, module.ok.zip, servlet-cdi-test-jar.src.zip, servlet-cdi-test3.src.zip, servlet-cdi-test3.war
>
>
> CDI does not scan module with multiple jars. Only first jar is scanned.
> Workaround is to package everything in single jar file.
> To reproduce:
> {CODE}
> #download attached files
> #download and unzip wildfly
> cd wildfly-9.0.0.Alpha1-SNAPSHOT #or other version > 8.0.0
> unzip ../module.multiplejars.zip
> cp ../servlet-cdi-test3.war standalone/deployments/
> ./bin/standalone.sh
> # observe deployment fails
> # stop server
> unzip ../module.ok.zip
> ./bin/standalone.sh
> # observe deployment succeeds
> {CODE}
> The same scenario succeeds in both cases on EAP 6.2.x.
> module.ok.zip was created from module.multiplejars.zip by merging jar files into single one



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)