Hello Friends, I'm facing one problem while instantiating an EJB object. I have an object which implements javax.ejb.SessionBean interface. In this particular object, i put empty method definitions for javax.ejb.EJBObject interface. I know it is not a good practice of implementing methods of javax.ejb.EJBObject. But I had to do this in order to instantiate that object using new in some cases. I'm using WebSphere 3.5.4 Now when I try to instantiate that object, it throws exception com.inet.utility.ExceptionError: java.rmi.NoSuchObjectException: CORBA INV_OBJREF 0 No; nested exception is: org.omg.CORBA.INV_OBJREF: com.inet.core.SessionManagerBean not exported or is a JRMP stub minor code: 0 completed: No
Here SessionManagerBean is an object which implements javax.ejb.SessionBean interface and contains method definitions for javax.ejb.EJBObject interface. The same code was working fine in WebSphere 3.5.2 After applying fix pack 4, this problem started. Cant we use "new" for objects which implements SessionBean interface? Does container treat that call as a data access bean? Could you please help me out?
"nrbhattad", The Java Ranch has thousands of visitors every week, many with surprisingly similar names. To avoid confusion we have a naming convention, described at http://www.javaranch.com/name.jsp . We require names to have at least two words, separated by a space, and strongly recommend that you use your full real name. Please log in again with a new name which meets the requirements. Thanks.