If I understood your requirements correctly, you have:
1) A client written in Java running on WebSphere
2) A service running on an ORB
and you want the client to invoke the methods provided by the service. Right?
Now, if this is all there is, I can't see the reason for wrapping the CORBA operation inside an
EJB. Why did you use EJB in the first place? Has that particular requirement vanished or is it still valid? Are you using the EJB container to limit simultaneous connections to the ORB? On the other hand, what do you mean with "ejb/xml"? Are you sending serialized XML documents as parameters to the CORBA operations?
The simplest implementation would probably be to
1) compile the IDL file into a static stub class
2) use this generated stub class from your Java code to invoke the service's methods
Finally, don't take my
word for it - I have only coded CORBA stuff with C/C++ (using the open source MICO), and even that exposure was quite limited.