[ https://issues.jboss.org/browse/CDI-233?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-233: ----------------------------------- Martin, the whole bean archive stuff is completely the wrong direction! Instead of this broken BDA we need _real_ modularity! We need to target ClassLoader isolation and visibility rules and not BDA (which is exactly 1 BDA == 1 jar as per the spec). Even Weld in the last version does NOT implement the specified BDA behaviour. And this is good, because the spec is broken in this part. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/CDI-233?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-233: -------------------------- Fix Version/s: 1.1 (Proposed) Component/s: Portable Extensions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/CDI-233?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-233: ----------------------------------- I fear that would be dangerous. Think about EAR scenarios again. Adding them to a shared level would probably trash other apps. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/CDI-233?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-233: ----------------------------------- maybe we have different understanding about what 'shared library visibility' means. I take it as 'class which is contained in a shared ejb-jar. Of course. Adding a synthetic bean to a shared jar would make it visible to ALL other WAR files. That's not very defensive^^ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/CDI-233?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-233: ----------------------------------- imo we can only solve this cleanly once we defined how BeanManagers and their Extensions in multi-module projects get handled. And this discussion is not yet finished. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira