On Sun, 20 Jan 2002, Kimbro Staken wrote: > >On Sunday, January 20, 2002, at 07:23 AM, Heinrich G�tzger wrote: > >>> >>> As long as you have a POA compliant ORB this is trivial to do. I've >>> switched between OpenORB and JacORB many times while testing and other >>> people have used Visibroker as well. >> >> I tried with different orbs: OpenORB, JacORB, Orbacus and the java-builtin >> SunORB and got different results. Xindice seems to run with OpenOrb and >> SunORB very well, but using JacORB or Orbacus seem not to work. >> > >JacORB used to work fine, haven't tried it in a while though. No idea >about Orbacus. What is the error you get?
Ok, in the meanwhile I discovered, that I wasn't quite exactly correct describing my problem. I tried running the client with different ORBS, while the Server is running with OpenORB. So OpenORB and SunORB seem to work while JacORB and ORBACUS won't. Add 'Thread.currentThread().sleep(100000);' as last line in helloORB.java and send a kill -3 to the PID to get a thread dump showing which ORB is loaded. And, the more I think about it, the more I get the feling, that this is a very special kind of configuration at all. At least I have the dbXML running in xmlBlaster using two ORB's. > >> I added some example as attachment, showing how I testet it. Example1 is >> from the Xindice, slightly changed. All the commands I used are in >> helloORB.java at the end. >>> >> >> I'll take a look into xindice-xmlrpc as well. >> > >I'd probably rather put more effort into ramping other connectivity >options, instead of worrying too much about getting different CORBA ORBs >to work. right now we think about implmenting a classloader hirachy like described in: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/class-loader-howto.html to address the problems wich may occur with other plugins like security, protocol or persistence. There may also be problems with different XMLParsers in different packages. > Of course JacORB should work just fine, so I'm sure it's just a >small problem that can be resolved if you really want to go that route. Using JacORB would be fine for the first. Using jacorb: <corba class="org.jacorb.orb.ORB" singletonclass="org.jacorb.orb.ORBSingleton" /> it starts fine, but while I try to address the DB, following error occurs: Starting Xindice ---------------- Xindice 1.0rc1 (DarkHorse) Database: 'db' initializing Script: 'GET' added to script storage Service: 'db' started Service: 'GopherServer' started @ gopher://dynamite.exploding-systems.de:4070/ Service: 'HTTPServer' started @ http://dynamite.exploding-systems.de:4080/ JacORB V 1.3.30, www.jacorb.org (C) Gerald Brose, FU Berlin, 13 June 2001 [ POA RootPOA - ready ] Not found for [EMAIL PROTECTED] Service: 'APIService' started Server Running --> starting 'xindice lc -c /db' from another shell [ Accepted connection from 172.24.64.1:34440 ] Not found for [EMAIL PROTECTED] [ POA RootPOA - rid: 5 oid: 00 10 38 05 24 18 04 42 03 1A opname: getCollection - invocation: throwable was thrown ] ############################ StackTrace ############################ java.lang.Error: Bad codeset: 65568 at org.jacorb.orb.CDROutputStream.write_char(CDROutputStream.java:501) at org.jacorb.orb.CDROutputStream.write_string(CDROutputStream.java:527) at org.omg.IOP.IORHelper.write(IORHelper.java:124) at org.jacorb.orb.CDROutputStream.write_Object(CDROutputStream.java:792) at org.apache.xindice.client.corba.db.CollectionHelper.write(CollectionHelper.java:83) at org.apache.xindice.client.corba.db.DatabasePOA._invoke(DatabasePOA.java:104) at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:207) at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:404) at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:513) #################################################################### [ Closing connection to 172.24.64.1:34440 ] Thanks regards Heinrich -- http://www.xmlBlaster.org
