View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820650#3820650
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820650 Also. InvocationResponse is really only useful when going across network boundaries as there needs to be a way to piggyback metadata as well as propagating the return value or exception. This is not true. Moving a request across thread pools and service layers also requires that you do not maintain the strict direct call stack semantic. Routing choices and exception handling can be affected by metadata associated with the response. Also, having to choose how the return value/exception are propagated depending on whether or not there is a transport layer is a complexity that does not need to show up if there is an InvocationResponse. ------------------------------------------------------- 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
