On Wed, 12 Apr 2000, Laird Nelson wrote:
> Finally, I suppose that if I'm following the (excellent) suggestion of
> implementing a business interface (a superinterface of the bean class
> and the remote interface), I should simply not declare in the bean
> class' implementations of the business interface methods that they throw
> RemoteException. Or, to put it less confusingly, it should be the case
> that RemoteException should not show up in any throws clause in a bean
> class. Correct?
of course, you'll have to put in a "throws RemoteException" if your bean code
makes a call against the remote interface of some other bean. Because that
other bean's remote interface will surely throw a RemoteException. I
consider it best not to eat that RemoteException and throw EJBException but
instead to propagate out that RemoteException. In which case some of your bean
class methods *will* have to list RemoteException on their throws line.
cheers,
david
--
David Sims [EMAIL PROTECTED]
Sims Computing, Inc. www.simscomputing.com
===========================================================================
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".
