Just to round off the discussion and what I think we agreed. 1) The MC will inject dependencies into GenericBeanFactories where advices need injections. These GBFs will be used by a generic aspect factory to construct the advices as required according to scope.
2) The MC needs to know about the @Dependency annotations of the class and the relevent AspectFactories names so it can correctly workout the dependency order as it starts services. 3) There will be an aspect deployer that does xml -> MC config to construct and install Aspect metadata instead of the AspectXMLLoader/Deployer The advice dependcies can be defined through a) annotations on the advice class using (2) above b) annotation overrides in the MC config c) plain MC depends xml config View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871410#3871410 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871410 ------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
