RemoteException deprecation and EJBException

Question

Is throwing a RemoteException from remote interfaces a deprecated
programming practice?
I've read some articles and newsgroups which stated that.
If true, since when exactly is this deprecated?
Remote interfaces implement java.rmi.Remote so they must throw a
RemoteException, don't they?
Should I throw EJBException instead of RemoteException?
Any remarks, explanations would be greatly helpful.

Answer 1

Exactly.
The container implementation of your remote interface will throw a
RemoteException or javax.transaction.TransactionRolledBackException
(which is an instance of RemoteException) if you throw an EJBException
from your Bean implementation.
If instead you use a Local interface, then you should either get the
EJBException or javax.ejb.TransactionRolledBackLocalException (which is
an instance of EJBException).
It's a bit complicated and I might have been unclear myself for which I
apologize.
HTH,
Dejan
Yonatan Taub wrote:
I don't quite follow.
Do you mean that my remote interface class should declare that it throws a
RemoteException while my bean implementation class
should not state in its throws clause a RemoteException?
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
EJB 1.1 Spec deprecates throwing RemoteExceptions from the Bean
implementations.
EJBs can still throw it and the container should behave in the same was
as if an EJBException was thrown.
The difference is when all this happens if your EJB has a Remote and
Local interfaces. The local clients (those using the local interface)
should get the EJB exception that might be wrapped in a
TransactionRolledBackException to indicate that the current transaction
was rolled back, while the remote clients should get the EJB exception
(or any RuntimeException thrown from your EJB implementation) wrapped in
a RemoteException.
HTH,
Dejan
Yonatan Taub wrote:
All of this is known to me.
Since then I read some more material on the subject.
It seems that throwing a RemoteException from a bean implementation
class
is deprecated.
RemoteException indicates a system exception and the bean implementation
class should throw an EJBException.
The container specific implementation would catch this exception and
throw a
RemoteException.
http://groups.google.com/groups?q=ejb+RemoteException+deprecated+ejbexcepti
on&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=8i5b64%24bk8%241%40newsgroups.bea.com&rn
um=4
I would appreciate your thoughts on the subject.