"[EMAIL PROTECTED]" wrote : | This @Dependency annotation only tells the MC about the dependency. The MC doesn't know how/where this dependency should be injected. The @SecurityDomain is on the bean class and it is the aspect that needs this information to lookup and set the dependency within the aspect. A distinct, non-GenericBeanFactory implementation of an AspectFactory would be needed here. It would work the same way the Security aspect works now in the current impl except that they MC would be able to hold up bean creation because the SecurityDomain dependency would be published to it via the @Dependency annotation. |
Correct, the @SecurityDomain tells the MC the correct order for instantiation. The advice does not change its implementation. I think this is a major requirement. i.e. none of our changes should affect user code already in existance. What we are changing (hopefully improving) is the way and the possiblities they are configured/managed. In the security domain case, it will still use jndi as now, though as Scott pointed out in a different thread, the implementation could be improved to avoid the dependency on jndi. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871412#3871412 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871412 ------------------------------------------------------- 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
