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.
I am not sure weather this topic has been covered earlier. If it is plese post me the link.
I am trying to call a Session EJB from a client. Both the client and EJB are on two physical locations on WebSphere4.0. The Session EJB has a reference to some DataBean called com.test.pricing.SomeData, which is available in a separate jar file. On client side I have a jar file containing the stubs for the session ejb.
While invoking this Session Bean from client the program throws Exception: org.omg.CORBA.NO_IMPLEMENT: Unable to locate value class com.test.pricing.SomeData minor code: 1 completed: Noat com.ibm.rmi.iiop.CDRInputStream.read_value(CDRInputStream.java:1377) If I provide the jar file containing com.test.pricing.SomeData, at the client side. The exception dosen’t come. I have certain questions regarding this behavior. 1. If we assume that the session bean class executes at the server side, why is the client code is looking for Data Object at the client side? 2. Prior specifications of Corba doesn’t support call by value, is it because of that we have to provide any Data Objects used by EJBs in their bean implementation at the client side.
SCJP, SCJD, SCWCD1.4, IBM486, IBM484, IBM 483, IBM 287, IBM141, IBM Certified Enterprise Developer - WebSphere Studio, V5.0
Author of IBM 287 Simulator Exam
Since the question is related to EJB as well as Websphere, I tried to address it to both the forums. I thought maybe a different set of professionals might access EJB and websphere Forums. Pretty Logical
Joined: Jan 27, 2004
You potentially waste repliers' time cross-posting though. It is against the policy of the forums for this reason. Person A might answer you on this post, and person B answer you on the other one, unaware that it was already answered. Pretty logical
Vijay S. Rathore
Joined: Oct 29, 2001
You just gave a reference to another thread also, solving the problem. Moreover I think, this problem should be addressed by the implementors of the forum. They can restrict multiple postings using something like Synchronize.
But don't you think we are deviating from the objective here?