On Wed, 12 Apr 2000, Richard Monson-Haefel wrote:
> Laird Nelson wrote:
>
> > >From what I've read in section 12.2.2, it looks like RemoteException
> > should basically not be thrown from any method in the bean class, if at
> > all possible. Instead, an EJBException should be thrown instead.
> >
> > Was it the specification's intent to *replace* the throwing of
> > RemoteExceptions with the throwing of EJBExceptions, or was it its
> > intent to *augment* it?
> >
>
> The intent is to replace it. EJBException should be thrown from EJB 1.1 beans
> instead of RemoteException. RemoteException was left in the method signatures
> to support backward compatibility with 1.0 beans.
(just to clarify a bit)
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. So it's not to say that we should never, ever have to
deal with RemoteExceptions again.
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".
