RegistryIntf extends the java.rmi.remote Interface.
And Registry class Inplements the RegistryIntf and extends PortableRemoteInterface. I am using RMI-IIOP.
I am using Visibroker Naming Service , and also using the Borland Appcenter to manage my Components.
First I compiled my Registry.java .
Next I do java2iiop on the RegistryIntf class. It generates al the POA's Stubs and Ties for the RegistryIntf.
In the RegistryIntf I am using the customized API classes provided to us to register to Naming Service. (I am not using the API's provided by the Visibroker).
Now i prepare a JAR of all the files , and run the Registry class from console , it gave me the exception Registry_Stub not found.
Next I took the same jar and put it into my Borland Appcenter Configuration and make that as a separate component , and then started this from Appcenter . The Component Started correctly and registers itself to the Naming Service.
So can any one tell me why StubNotFound Exception is thrown when i run the Registry class from the console, and the same class runs fine in the Appcenter.
Please let me know if you have any doubts in my above explanation.
This sounds like it's either a classpath problem, or a problem with not setting some needed system property... What's the full command you are using to run from the console? What do you have your classpath set to in the console?
Write once, run anywhere, because there's nowhere to hide! - /. A.C.
Joined: Aug 13, 2004
The thing is that I have not generated the Regisrty_Stub class. When i run java2iiop on the RegistryIntf, the Stubs and the Tie classes of the RegistryIntf are generated .
So my question is that why the program is giving exception in console while it is running fine as a component in Appcenter
I haven't used AppCenter before, but the only thing I can think of is what I said before - that AppCenter is setting some kind of system property, or knows how to set up the classpath based on what you provide it - and that this isn't getting done when you run from the command line.