Well, uhm, not really... The call stack is:
invocation handler::handleCallback() -> server callback handler (internal to remoting) -> remoting callback client -> network So the exception will be bubble up through the server callback handler before the invocation handler (user code). I will just make so if this happens, the server callback handler will remove itself from the server invoker and the invocation handler and that will be the end of it. This way, everyone on the server side will be aware that it has been removed. Only problem is that the client will not be aware that it has been removed in the case that there was a temporary network outage on the client side. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865762#3865762 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865762 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
