RemoteException vs EJBException

[Raghothaman Nagarajachar]

Hi
In EJB 2.0 specification, it is mentioned that the use of java.rmi.RemoteException was deprecated for container-invoked callbacks (like ejbCreate, ejbPassivate, ejbActivate) and must use javax.ejb.EJBException instead.
But when I create a new EJB 2.0 component with java.rmi.RemoteException, build and deployment was successful. Also with javax.ejb.EJBException, build and deployment was successful.
This means can we use either of these exceptions in EJB 2.0....?
Is it not necessary to replace java.rmi.RemoteException with javax.ejb.EJBException ....?
Thanks
Raghu

[Rahul Mahindrakar]

In EJB 2.0 specification, it is mentioned that the use of java.rmi.RemoteException was deprecated for container-invoked callbacks (like ejbCreate, ejbPassivate, ejbActivate) and must use javax.ejb.EJBException instead.

The term that is important here is "deprecated". The term deprecated means that it is supported for now, but in future it may no longer be supported.
Thus you have written code that works for now. But in future your code may not work!!!

[Raghothaman Nagarajachar]

Thanks for your answer.
Will replace RemoteException with EJBException.

[Rahul Mahindrakar]

Hi,
You do not need to throw EJBException as it is a runtime exception.