Hi Audrius, > >Exception in thread "Thread-6" org.omg.CORBA.MARSHAL: Not a GIOP message > >Minor: 0 (0). Completed: not completed > > at gnu.CORBA.GIOP.MessageHeader.read (MessageHeader.java:288) > > > > > This means that Classpath is reading not a CORBA message but something > different. All CORBA messages begin with the standard magic character > sequence "GIOP". The exception is thrown when the incoming message > begins differently. > > In the past, I had plans to connect ORBit from Classpath using our > implementation, but then found on the web that the direct communication > is not possible because ORBit uses additional *authentication protocol. Hmm. AFAIK Corba/ORBit is a standard communication between gnome apps, I cannot think that they need to authenticate or something like that. > *It is important for us to know how did you achieved the working > connection between ORBit and Sun's implementation. Did you put any > additional system properties like org.omg.CORBA.ORBClass? If yes, and if > the ORBit classes are present in your path, the Sun's jre is probably > just running ORBit CORBA internal implementation classes. I don't think so. I had to put the following into ~/.orbitrc: ORBIIOPIPv4=1 which enables orbit communication via TCP/IP. Besides that I had to do nothing special. I suggest you try it out yourself. You can find the sourcecode to the java-access-bridge here: http://ftp.gnome.org/pub/GNOME/sources/java-access-bridge/1.5/ Simply ./configure and make should compile a .jar file (don't make install, this will copy stuff into some jdk dir, which you probably do not want). However, you'll need the Sun JDK for this, it needs the idl tools. You'll also need a couple of header files in your system. I have uploaded my compiled jar here: http://kennke.org/~roman/gnome-java-bridge.jar maybe this will do for you to try. Then you need to put the following into ~/.accessibility.properties : assistive_technologies=org.GNOME.Accessibility.JavaBridge This only tells the java.awt.Toolkit to load the specified class when it starts up. This triggers the setting up of the bridge. You also have to configure GNOME to enable accessibility features, otherwise nothing will happen. If you've done all this, you can start up a Swing application (like our demo) normally. If everything is good, then there should be some messages about the bridge registering with the gnome accessibility framework. This is the point where we fail. Thinking about it, it might be possible that the connection originates from the GNOME side. I notice that when I have accessibility enabled in gnome, and fire up jamvm with a Swing app, I get a message about GTK accessibility activated or something. I think the GTK could notice that a GTK using application fires up and possibly trigger the accessibility stuff to register itself. But what do I know about the internals of GTK/accessibility? ;-) However, I'm quite certain, that the bridge does use nothing special and establishes communication to ORBit using the built-in CORBA from Sun. I hope this helps. I think it would be very nice to be compatible with CORBA and to be able to bridge Free Java to the Gnome accessibility framework, using only free software. /Roman -- ?Improvement makes straight roads, but the crooked roads, without Improvement, are roads of Genius.? - William Blake -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: Dies ist ein digital signierter Nachrichtenteil Url : http://developer.classpath.org/pipermail/classpath/attachments/20060406/80339db7/attachment.pgp
