CORBA.BAD_OPERATION

Question

I am getting this error and don't understand why. I'm a relative novice to CORBA. I am using JDK 1.4.1_05 on XP.
I generate my IDL files using idlj -fall and idlj -fallTIE.
I get the standard generated files -
_ImageSessionStub.java, ImageSession.java, ImageSessionHelper.java, ImageSessionHolder.java, ImageSessionOperations.java, ImageSessionPOA.java, and ImageSessionPOATIE.java
I am trying to call the getImageServiceDM method. That method is present in the _imageSessionStub, ImageSessionOperations, ImageSessionPOA, and ImageSessionPOATIE files.
Here is the code I use. The variables "orb" and "poa" are already initialized. The "orb" is the one created in my server. The "poa" is the RootPOA.
ImageSessionImpl extends IMAGE_SESSION_POA and has the method getImageServiceDM defined.
org.omg.CORBA.Object obj = orb.resolve_initial_references("NameService"); 
NamingContextExt ncRef = NamingContextExtHelper.narrow(obj);
ImageSessionImpl imageSessionImpl = new ImageSessionImpl();
ImageSessionPOATie tie = new ImageSessionPOATie(imageSessionImpl, poa);
Image Session ImageSession il_href = tie._this(orb);          At this point, il_href is a _ImageSessionStub object.
The CORBA.BAD_OPERATION exception occurs if I then issue:
RRISImageServiceDM rIsImageServiceDM =
         il_href.getImageServiceDM();I can see it goes into the stub but it dies in the _invoke method.
I didn't know if I needed the following code but I commented out the above statement but I had the same outcome.
NameComponent[] il_nc = ncRef.to_name( imageSessionImpl.getName());
ncRef.rebind(il_nc, il_href);
imageSession = ImageSessionHelper.narrow(
                                     ncRef.resolve_str(imageSessionImpl.getName()) );
Again, the CORBA.BAD_OPERATION occurs here:
RRISImageServiceDM rIsImageServiceDM =
         imageSession.getImageServiceDM();Again, imageSession is a _ImageSessionStub object.
Any suggestion/ideas would be appreciated. I know I must be missing something basic.
Thanks

Answer 1

I think minor codes are vendor specific. Last time I needed to know this information, I had to go look at the source...