James Cook wrote:
>
> I don't see any design pattern that would achieve the behavior I am looking
> for. The problem boils down to the rule in the spec that states each method
> in an EJB remote interface must throw RemoteException.
I don't see the problem. Although methods on the remote interface must contain
"throws RemoteException", there is no obligation for the bean (implementation)
class to throw RemoteExceptions. In fact this is deprecated in EJB 1.1, in
favour of throwing javax.ejb.EJBException, which is supposed to be derived
from java.lang.RuntimeException (although it doesn't have this inheritance
relationship in the EJB 1.1 JAR file I have at hand.)
________________________________________________________________________________
Evan Ireland Sybase EA Server Engineering [EMAIL PROTECTED]
Wellington - New Zealand +64 4 934-5856
===========================================================================
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".
