I have an EJB 3 Stateless session bean instance and I have a client that is written to EJB 2.x Stateless session bean. Now as per the promise of EJB 3, this same client written for EJB 2.x should also be suitable for EJB 3 Stateless bean. So in such a case, how would I handle my RemoteException in my client (originally built for accessing EJB 2.x) which is targetting a EJB 3 Stateless bean because in my EJB 3 Remote Interface I do not have to explicitly say that I throw RemoteException?
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
The container certainly does the byte code enhancement, but that is during deployment. How can I handle RemoteException in my client when the methods in the interface that is marked @remote does not throws RemoteException. I mean how to add a catch block to handle RemoteException when my @Remote interface methods does not throw them during compilation time?