Howdy -- in EJB 1.0, you (bean developer) *could* declare (and thus throw) RemoteException from your methods, but this was deprecated with EJB 1.1.
I think the main reason was that RemoteException is really meant as a system exception, not an application exception, and the standard now is to use EJBException as the mechanism for communicating ALL system exceptions to the Container. Which means of course that if you *catch* a RemoteException in your bean methods, you must rethrow it as an EJBException.
The reason behind this is that it makes your bean code more open: if you would throw a RemoteException you can't expose the method in a local home/component interface.
If instead you throw a EJBException you can, if the interface is remote the container will wrap your EJBException in a RemoteException.
Hi Paulus, When we say home methods, these methods are defined in the interface extending from EJBHome or EJBLocalHome. How can we have an option of exposing the home methods in local home or remote home? Pls explain. Thanks Shobha SCJP 1.2, SCWCD