This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hi We are planning to migrate our application from JDK 1.1 to 1.3. Some methods are deprecated in the new version. I learnt that we can still use the old deprecated methods and it will compile without any error. The problem will arise only if the methods are removed in the later (higher) releases. If it is only deprecated we can still use it and compile. This is what I heard. Similarly we are planning to migrate from EJB 1.0 to EJB 2.0. I learnt that java.rmi.RemoteException is deprecated and replaced by javax.ejb.EJBException for EJBCreate, EJBPostCreate, EJBRemove, EJBActivate, EJBPassivate, SetSessionContext in EJB 1.1/2.0. But can we still use java.rmi.RemoteException for these methods in EJB 2.0........? We are upgrading the EAServer and PowerJ from 3.5 to 4.1. Any guidance / comments will be highly appreciated. Thanks Raghu
First, please note that your name does not meet the requirements of the JavaRanch naming policy (http://www.javaranch.com/name.jsp). Please change your display name. Thanks. Second, according to an interview I read with one of the lead guys at Sun, they have no plans to remove deprecated methods from the language. Third, "Enterprise beans written for the EJB 1.1 specification should throw the javax.ejb.EJBException instead of java.rmi.RemoteException. Enterprise beans written for the EJB2.0 and higher specifications must throw the javax.ejb.EJBException instead of java.rmi.RemoteException."