I notice in the .xdt file responsible for generating the remote interfaces for EJBs, that the template explicitly adds the java.rmi.RemoteException to each method in the remote interface and skips over the javax.ejb.EJBException.
 
After reading through the EJB 2.0 specification again, my understanding is that throw EJBException is correct if writing a v2.0 bean and RemoteException should only be thrown if you want to v1.0 compatible.
 
Is there are reason this template is hard coded to throw RemoteExceptions instead of having the option to throw EJBException instead?
 
Thanks
 

Reply via email to