"timfox" wrote :
| Why do RuntimeExceptions/Errors need to be wrapped in a JMSException and sent to the
client?
|
| Can't we just propagate the RuntimeExceptions/Error as is to the client?
Errors yes/maybe - they are normally non-recoverable,
but that doesn't mean you shouldn't try, otherwise
the whole system could go into an indeterminate state.
There are many errors that might only be related to a specific request,
e.g. NoClassDefFoundError when unmarshalling an object message.
However, if the user passes bad parameters
then the appropriate exception should be thrown.
Any RuntimeException after you accepted the request is your problem,
it should be reported to the user as a JMSException, even
though it is likely fatal.
How do you pass that Error/RuntimeException to onException()?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961372#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...