"adrian(a)jboss.org" wrote : | I suspect that longer term we'll want some way of retrieving what Seam does | to resolve the ejb so we can properly manage cross deployment | dependencies that Seam creates. | The only thing that I can see us doing is checking to what all we can map @In annotation. e.g. is there some existing EJB that we can map to using field's name | public class SomeSeamComponent | { | @In | private PaymentManager manager; | } | and then use AnnotationEnvironment.classHasFieldAnnotatedWith(In.class) (where In.class must come from unit's classloader). Then we iterate over all fields, checking if we can do some mapping. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155374#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...