[weld-issues] [JBoss JIRA] Commented: (WELD-778) Weld must be able to support extension discovery in the modules of an multi-module application (EAR)

[ https://issues.jboss.org/browse/WELD-778?page=com.atlassian.jira.plugin.s... ] Pete Muir commented on WELD-778: -------------------------------- Mark, can you expand on (a) BDAs infringe on other EE specs? This sounds like a problem. Otherwise most of what you say is somewhat circular as you complain about the lack of classloading structure definition in EE, and then go on to complain about the way CDI get's around this lack of structure. In neither CDI nor Weld can we define the classloader structure for EE, so we need to be able to get around it. I am happy to listen to alternative proposals which could augment/replace bean archives, however I don't see them as that much of a problem (yes, it has been hard to impl and hard to get consistent behavior across platforms, but I think this has little to do with bean archives, and everything to do with the variations in classloading). It is clearly defined what an application is in Java EE, please refer to chapter 8 of the Java EE specification. Figure EE.8-1 gives a clear overview of this, describing the EAR as the Java EE application. Of course, when a war is deployed outside of an EAR, it constitutes an application as defined by the servlet spec. This area is not in doubt, and AFAIK there is no confusion here, I have never seen a general concern about this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira