Join jp compilation and stub generation

[Bernhard Haumacher (haui at haumacher dot de)]

The KaRMI stub and skeleton generator is build into the gj compiler and uses its data structures to access the remote class for which the stubs and skeletons are build. This requires the remote implementation class to be already compiled before the stubs and skeletons are build. When obviating the stubs, the handle class uses the stub class to determine the method numbers (ticket:195). But the implementation classes use the handle class in the instantiation process of new remote objects. Therefore the implementation classes can no longer be compiled before the stubs are generated.

Solution

The stub and skeleton generator must be modified to offer an interface that does not depend on internal compiler data structures, because these are only available after the implementation classes are compiled. In contrast this interface should expect the necessary information as character strings which can be produced from the original JavaParty classes.

partially-fixed since 1.03c.
First version after restructuring. Simple method invocation already works (uka.test.karmi). Integration into JavaParty not yet tested. Remaining problems: ticket:28

fixed since 1.03h.