If the flow of the exception is: client -> invocation handler -> core remoting
The invocation handler can choose to filter what exceptions are handled by the core system and/or handle it itself. Any exception that does make it back to the core system should be assumed to be a failure and the client removed. NOTE: The application (invocation handler?) that has exposed the remote object will still need to know about the removal. e.g. JMS will need to delete temporary queues/topics and non durable topic subscriptions. You might want to introduce a generic handler that understands the transport and what is recoverable. This can work across all invocation handlers, e.g. client -> transport specific error handler - > invocation handler -> core remoting Is this a good enough translation Tom? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865758#3865758 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865758 ------------------------------------------------------- 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
