A) rmic -iiop (generates Java stubs and ties from Java classes) B) a Cos name server (corresponds to tnameserv in the Sun JDK) C) idlj (converts from IDL to Java stubs and ties) D) rmic -idl (converts from Java remote interfaces to IDL)
A & B are absolutely necessary to have a working remoting system. One of the reasons to use IIOP with Java is IDL, so C & D are probably important to most users of IIOP.
Building A, C, and D from a single codebase would allow for significant code sharing among the tools. All 3 work with the IDL and Java metamodels and need to translate between them. This translation is a big part of the complexity of the tools. No open source project that I know of has taken advantage of this opportunity for code reuse; Classpath can do this and implement the IDL-Java translation logic once and for all.
Various pieces of IIOP tools functionality are already implemented in other open source projects. I am aware of JacORB and ObjectWeb's Jonathan [2]. Both are LGPL licensed. Jonathan has a somewhat functioning A. JacORB provides B, though it is missing one feature (the ability to specify a known initial port). The two subflavors of C (default and -poa) are provided by Jonathan and JacORB respectively. I do not know of a D.
-- Archit
Links:
1. http://www.jacorb.org 2. http://jonathan.objectweb.org
_______________________________________________ Classpath mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath
