If bean method X's implementation uses another bean Y, and X cannot recover
from a system exception (delivered as a RemoteException to X),
then the 1.1 specification implies that X should wrap the RemoteException
from Y in an EJBException.

What is the benefit over just declaring RemoteException in X's throws
clause?

In either case, X's client gets a RemoteException. Y's system exception has
already been logged by the container.  Wrapping the exception just clutters
the code and the system log.

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to