"alesj" wrote : | "pete.muir(a)jboss.org" wrote : | | * using an ejb-jar not deployed inside the app, but deployed at the top level | | | You mean we should be able to track external EJBs and add them as accessible BDA? | | How does this again play with all listed BDAs and circularity problem? | e.g. if I list it in one WB app Deployment/BDAs, I them must exclude it in another (its original app) ... Exactly, this is why Web Beans allows the container to put circularities into the BDA graph. Inside Web Beans we remove the cycles by removing the first BDA to reoccur when we walk a particular path by tracking what BDAs we have already seen in this path. This is why the Javadoc says "Circular dependencies will be detected and ignored by the container" - thats not very clear, it now says "Cycles in the accessible BeanDeploymentArchive graph are allowed. If a cycle is detected by Web Beans, it will be automatically removed by Web Beans. This means any implementor of this interface don't need to worry about circularities." Note that the graph can only be changed during deployment, at runtime it is static and we can cache the transitive closure of BDAs a BDA can access which means we have low overhead. Of course, the container may already have a non-circular structure in place, so that could be anonymous wrote : "pete.muir(a)jboss.org" wrote : | | * using extensions defined in manifest.mf http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html#Main%20At... and [url]http://java.sun.com/javase/6/docs/technotes/guides/extensions/spec.html | | | This looks like normal manifest lib listing, and is already supported - while building classpath. | Hence it should already be included in the recent new impl. Great. We will add some TCK tests soon to verify this deployment structure, so we'll get results then :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246749#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...