[ https://issues.redhat.com/browse/WFLY-14143?page=com.atlassian.jira.plugi... ] Matěj Novotný commented on WFLY-14143: -------------------------------------- Hello, sorry it took me so long to get to this, but other priority items kept popping up. After testing your reproducer (thanks for that BTW!) I came to a conclusion that this is actually a configuration error, not a bug. Let's first look into how you make it work - the MANIFEST file in your WAR needs to declare the following dependency (mind the meta-inf affix) - {{Dependencies: org.example.mymodule meta-inf}} This can be achieved via maven war plugin inside your {{MyWar/pom.xml}} in the following way: {code:java} <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>3.2.0</version> <configuration> <failOnMissingWebXml>false</failOnMissingWebXml> <archive> <manifestEntries> <Dependencies>org.example.mymodule meta-inf</Dependencies> </manifestEntries> </archive> </configuration> </plugin> </plugins> </build> {code} Your JAR (the library) shouldn't need this declaration. The fact that it worked in earlier versions of WFLY was actually a bug; one that was reported and fixed in WFLY-13641. With this fix in place, all deployments now need to declare that meta-inf dependency if they want to use beans from other deployments (either via MANIFEST or via jboss-deployment-structure). All of the above is documented here - https://docs.wildfly.org/21/Developer_Guide.html#CDI_Reference Hope this makes it clear, please ask away if that's not the case. Meanwhile, I will close this issue as it is not a bug. -- This message was sent by Atlassian Jira (v7.13.8#713008)