View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820669#3820669
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820669 "marc fleury" wrote : on the topic of return interceptors. Try catch is ok but the important point is interceptor variable visibility across in and out. For example think TX interceptor, the behavior of the interceptor on the OUT part depends on the IN part (was there a transation in a REquires NEW mode?). If you don't have one instance dealing with that, you are stuck with stuffing that information in the invocation object and retrieving it on the way out. IN/OUT separation of interceptors make it just more complex to write for not functional advantage (that I can see) I agree with Marc. 99% of use cases wil not want to chance the interceptor stack. try/catch simplifies the programming model. 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
