aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes CORBA Exception Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "CORBA Exception" Watch "CORBA Exception" New topic
Author

CORBA Exception

Vijay S. Rathore
Ranch Hand

Joined: Oct 29, 2001
Posts: 449
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
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: CORBA Exception
 
Similar Threads
Here is the complete JBoss Config. for EJB
CORBA Exception
Test 488 questions
long post IBM.158
EJB lookup problem on WebSphere