[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... ] Mark Struberg commented on WELD-778: ------------------------------------ The whole BDA definition is completely against any other EE spec out in the wild anyway. So please let's just get rid of this whole BDA nightmare. There is one really well working classloader configuration available with 1 CL for the EAR + 1 child classloader for each webapp. But this (and other classloader scenarios) is afaik not specified in any EE spec. The problem starts that there is are old and very insane classloader configurations which just share classes even amongst different EARs (figured recently on JBossAS5), etc. This is imo pretty sick and every little jetty and tomcat offer better (== more secure) classloader isolation. We imo should _not_ propagate those _bad_ classloader habits but instead either a) kill all the BDA definition (which currently infringes other EE specs) or b) finally start defining a (default) standard ClassLoader schema in EE7 and build our behaviour upon this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira