FULL JDK VERSION(S):
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode)
The Java-to-IDL specification supported by J2SE 5.0 (ptc/00-01-06, as
referred to by http://java.sun.com/1.5.0/docs/guide/idl/compliance.html)
says (in section 1.4.6):
The stub class corresponding to an RMI/IDL interface or implementation
class may either be in the same package as its associated interface or
class, or may be further qualified by the org.omg.stub package prefix.
For example, the stub class for an RMI/IDL interface class a.b.Fred
would be named either a.b._Fred_Stub or org.omg.stub.a.b._Fred_Stub.
For an RMI/IDL implementation class x.y.Z, the tie class would be named
Therefore, the Tie class should always be in the same package as the
implementation class; they should never prefixed with the "org.omg.stub"
However, for implementation classes in the javax.* namespace, the reference
rmic generates Tie classes with the "org.omg.stub" package prefix, and the
reference ORB implementation looks for the Tie classes in this location.
For example, an implementation class javax.management.WombatImpl has a Tie
class generated called org.omg.stub.javax.management._WombatImpl_Tie .
As neither the reference rmic nor the reference ORB is compliant with the OMG
specification, a spec compliant ORB will not find Ties generated by the
reference rmic, and spec compliant Tie classes will not be found by the
reference ORB implementation.
A similar problem (for classes in the com.sun.* packages) was reported under
sunbug 4959550. It's evaluation (on 2004-01-09) noted that the behaviour for
classes in both com.sun.* and javax.* packages prefixes was incorrect.
However, the fix made under that sunbug (made for J2SE 5.0) only addressed the
issue for com.sun.* classes.