> But of course, should one bean call another bean and encounter
network
> problems, a RemoteException will be thrown and the bean
should propagate it
> out, one way or another.
Yes, a bean that calls another bean must propogate a
RemoteException if it can not recover from the failure. However,
the specification (again 12.2.2) is clear on how this should be done:
"If the bean method performs an operation that results in a checked
exception that the bean method cannot recover, the bean method
should throw the javax.ejb.EJBException that wraps the original
exception."
So a bean method should not take advantage of a
RemoteException that happens to be in its signature to propogate
the RemoteException it might receive from a call to another bean.
Instead, it should catch this RemoteException, wrap it, and throw
an EJBException.
That having been said, there are no immediate consequences for
failing to do this. 12.3.7 mandates that the container support the
use of RemoteException as if it were EJBException. The only
problem that I can see is that a future version of the EJB
specification may no longer mandate support for this deprecated
use of RemoteException. Buyer beware.
-Dan
===========================================================================
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".
