Flavia Rainone [http://community.jboss.org/people/flavia.rainone%40jboss.com] created the discussion "Implementing a non-flat deployment for Weld Integration" To view the discussion, visit: http://community.jboss.org/message/541531#541531 -------------------------------------------------------------- This thread is for https://jira.jboss.org/jira/browse/WELDINT-1 WELDINT-1. Taking a look at how the deployers are implemented today, I figured I should start by creating a non-flat version of WeldDiscoveryEnvironment first, so we could have a new environment input fot the new non-flat Deployment implementation. There a few assumptions I'm making right now that I would like to validate: - the deployment continues to exist per top level only, the only difference we are going to have is in the BeanDeploymentArchives (BDAs) - if Deployment.loadBeanDeploymentArchive requests for a non-existing BDA, I should search for all archives in the deployment that are not currently BDAs. If one archive containing the requested class is found, I create a BDA for it and return it. If the assumptions above are correct, the main question I have right now regards two different deployments that can see each other. So, in the scenario described by the Deployment interface javadoc example, whereas we have ejb-jar A and ear B. This is going to be translated in two different deployments, each one containg one or more BDAs (in the case of the ejb-jar, one BDA only). Since those BDAs can see each other, there must be a way for me to reach Deployment A BDAs from Deployment B BDAs. Is there some SPI in the current implementation of weld integration that supports that? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541531#541531] Start a new discussion in JBoss Microcontainer Development POJO Server at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]