[omniORB] java and omniNames
baileyk@schneider.com
baileyk@schneider.com
Mon Nov 18 14:31:02 2002
I think the comment about jdk1.3 refers to the JavaIDL ORB. The Visibroker
ORB would not necessarily be impacted by that at all. I don't think the
JavaIDL ORB even supports the INS until j2sdk 1.4.
Kendall
Heinrich Götzger
<goetzger@gmx.net> To: omniorb-list@omniorb-support.com
Sent by: cc:
omniorb-list-admin@omniorb-s Fax to:
upport.com Subject: Re: [omniORB] java and omniNames
11/17/2002 02:45 PM
Please respond to Heinrich
Götzger
On Fri, 15 Nov 2002, Warren Brown wrote:
>It seems that jdk1.3 has a bug in it.
>>From the bug list
>"After digging deeper in the problem (thanks to the "genior" utility
provided
>with omniORB 3.0, I could generate many different kinds of IORs), I
discovered
>that the problem comes from the length of the Object Key ("NameService"),
>whenever the IOR contains an object key which size is not multiple of 4, I
get
>that exception."
>
>It seems that the solution to my problem is either to use jdk1.2.2 or
jdk1.4.
hmm, I'm using Java Visibroker 4.5.1 with JDK 1.3.1_06 under Linux being
served by a C++ Server with omniOrb 4.x using omniNames.
excerpt from my Java client:
[...]
System.setProperty("ORBInitRef"
,"NameService=corbaname::SERVERHOST:2809");
System.setProperty("org.omg.CORBA.ORBClass",
"com.inprise.vbroker.orb.ORB");
System.setProperty("org.omg.CORBA.ORBSingletonClass",
"com.inprise.vbroker.orb.ORBSingleton");
NamingContextExt nc;
try {
// Initialize the ORB.
orb = ORB.init( (String[])null, System.getProperties() );
// Obtain the root context.
nc = NamingContextExtHelper.narrow(
orb.resolve_initial_references("NameService"));
} catch (Exception e) {
e.printStackTrace();
}
[...]
in ominORB.cfg:
InitRef = NameService=corbaname::SERVERHOST
regards
Heinrich
_______________________________________________
omniORB-list mailing list
omniORB-list@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list