&quot;adrian(a)jboss.org&quot; wrote : | i.e. When I deploy my factory or some other container, | I also want the dependencies on a given class resolved before the factory is deployed. | | | | <bean name="MainClass" class="com.acme.Main"> | | <related>com.acme.Related</related> | | </bean> | | | | This was initially raised for AOP where we need to know that com.acme.Main | instantiates a com.acme.Related programmatically and that Related has aspects | whose dependencies need to be satisfied before we deploy/invoke on Main. | Should I then add a Set<String> related to BeanMetaData? How to generically handle this related? e.g. beanfactory's related bean should be scanned for MC's IoC annotations, but when there is related item for non-beanfactory we shouldn't scan for IoC, it should only be used for AOP dependencies View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142088#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...