cp-tools-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Cp-tools-discuss] Planning to check-in new branch: the GIOP extensions


From: Audrius Meskauskas
Subject: [Cp-tools-discuss] Planning to check-in new branch: the GIOP extensions for rmic.
Date: Mon, 06 Feb 2006 18:04:31 +0100
User-agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)

I have just finished writing the GIOP stub and tie code generator that is needed to develop the applications, using javax.rmi.CORBA package. It generates stubs and two required types of ties. I tested it with our x5 CORBA game: the generated stubs and ties seem interoperating well with the code, generated by the Sun's rmic.

Implementing this functionality fixes the bug 25704.

Initially, I wanted to put the new classed to cp-tools branch. However the cp-tools has the shared build system that (due gcj problems) seems not providing access to the necessary classes from org.omg domain. Also, the cp-tools project depends on several external libraries. From these libraries, ASM must be rather old (the v 2.0 is already not working, despite the v 3.0 is recently released), and Kawa must be manually reworked, forging bytecode.jar with FileRoller or other similar tool. As the GIOP code generator is currently not dependent from these two libraries, I would suggest to check in it in as a separate branch of the GNU Classpath project. As the generator cannot be currently compiled with gcj, it is built as the executable jar archive (runs both under Sun's jre and jamvm).

The source code is now uploaded to the bug 25704 as the proposed fix.

Regards

Audrius.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]