View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820670#3820670
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820670 "marc fleury" wrote : Letting a "manager" control the stack, rather than a self assembled list doesn't sound like a bad idea. I have seen this pattern in the past. It has the advantage of letting us control the stack through that manager. In JBoss AOP a "manager" does control the stack and injects it into the Invocation object. Then the individual interceptors have the option to change the stack. You don't want to have the ability to change the interceptor array directly as the "manager" shouldn't should be able to avoid allocating a new copy of the advice stack. When you get down to the pojo level this is extremely important. Bill ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
