[ https://issues.jboss.org/browse/WFLY-7252?page=com.atlassian.jira.plugin.... ] Teresa Miyar updated WFLY-7252: ------------------------------- Description: In an ear file 2 wars and one shared lib, warA provides implementation for shared lib, warB cannot see warA implementation even though our documentation on chapter 12 states: Chapter 12. Packaging and dep... • In an application deployed as an ear, the container searches every bean archive bundled with or referenced by the ear, including bean archives bundled with or referenced by wars, EJB jars and rars contained in the ear. The bean archives might be library jars, EJB jars or war WEB- INF/classes directories. Then we have this: See also the "5.1. Modularity", http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#selection: "A bean packaged in a certain module is available for injection, lookup and EL resolution to classes and JSP/JSF pages packaged in some other module if and only if the bean class of the bean is required to be accessible to the other module by the class accessibility requirements of the module architecture." "In the Java EE module architecture, a bean class is accessible in a module if and only if it is required to be accessible according to the class loading requirements defined by the Java EE platform specification." But the JavaEE spec states it "may" have access... it did have access on EAP6, does not have access on EAP7. was: In an ear file 2 wars and one shared lib, warA provides implementation for shared lib, warB cannot see warA implementation even though our documentation on chapter 12 states: Chapter 12. Packaging and dep... • In an application deployed as an ear, the container searches every bean archive bundled with or referenced by the ear, including bean archives bundled with or referenced by wars, EJB jars and rars contained in the ear. The bean archives might be library jars, EJB jars or war WEB- INF/classes directories. -- This message was sent by Atlassian JIRA (v6.4.11#64026)