On Wed, 12 Apr 2000, Richard Monson-Haefel wrote:
> Personally, I don't think its a good idea to blindly propagate RemoteExceptions (and
> other system exceptions) thrown with in a bean method to the client. You should
> attempt to handle the exception in an intelligent manner and throw an application
> exception if you can not recover or an EJBException if the problem is serious and
> requires the termination of the transaction and the eviction of the instance.
After reading Dan's and Richard's posts and reviewing section 12.2.2 of the
spec, it does indeed seem sound to me to not put "throws RemoteException" on
methods in the bean class. As Richard says, either deal with it and throw a
checked exception or don't deal with it and throw an EJBException, which will
rollback the transaction.
thanks everyone. I now know more about good EJB practices than yesterday. EJB is
an entire lifestyle, isn't it, not just a JavaDoc page. :-)
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".
