No, no, and no... This is not how we agreed how it would work and I really don't feel like walking through this again as we spent at least a day arguing through this stuff.
The ClassAdvisor controls when aspects are created, not the IoC container. AspectFactories have additional metadata (scope) on when and how many times they are created. Also, AOP has additional injected types that cannot be resolved through the IoC container and must be resolved by AOP when AOP decides to instantiate. So, IoC container will inject dependecies into the aspect via the GenericBeanFactory. The AOP ClassAdvisor needs to be able to lookup these GenericBeanFactories so it can decide when the Aspect is created. Also, aspect factories sometimes have no idea how to resolve dependencies until they are bound to the class they are weaving into. i.e SecurityDomain. Don't you remember going through this exercise? Anyways, please just answer my questions so that I can continue working... Bill View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871400#3871400 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871400 ------------------------------------------------------- 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
