-
Bug
-
Resolution: Duplicate
-
P3
-
6u4
-
sparc
-
solaris_2.5.1
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2167267 | 6-pool | Unassigned | P2 | Closed | Duplicate | |
JDK-2167268 | 5.0-pool | Unassigned | P2 | Closed | Won't Fix |
Writeup from Licensee
--
There are 4 helper classes missing in Sun JDK. They are
org.omg.CORBA.BoundsHelper
org.omg.CORBA.TypeCodePackage.BoundsHelper
org.omg.CORBA.TypeCodePackage.BadKindHelper
org.omg.CORBA.ORBPackage.InvalidNameHelper
The IDLtoJava spec clearly specifies the need of the helper class (not the Holder) for these files. But these are absent in the JDK. So, if we try to send any of these classes across in a client-server rmi-iiop model, it will throw an error complaining about the absence of the helper class.
Exact steps to reproduce
1. Write a remote interface with a method that throws any of these 4
exception classes, let it be Invalidname.
eg: public void sayHello( String str) throws java.rmi.RemoteException,InvalidName;
2. Write an impl class for this interface. Also, write an iiop server
which creates an object of this impl class and binds it with
NameService.
3. Write a rmi-iiop client which calls this remote method.
4. Now do an RMIC on the impl class.
Result:
It will throw an error, complaining about the absence of a helper class
for InvalidName.
Expected Result:
RMIC should create stub and tie classes sucessfully.
Exact text of any error messages
_HelloImpl_Tie.java:Undefined variable, class, or package name: org
org.omg.CORBA.ORBPackage.InvalidNameHelper.write(out,ex);
_HelloInterface_Stub.java:Undefined variable, class, or package name: org
if ($_id.equals(org.omg.CORBA.ORBPackage.InvalidNameHelper.id())) {
_HelloInterface_Stub.java:Undefined variable, class, or package name: org
throw org.omg.CORBA.ORBPackage.InvalidNameHelper.read(in);
3 errors
--
There are 4 helper classes missing in Sun JDK. They are
org.omg.CORBA.BoundsHelper
org.omg.CORBA.TypeCodePackage.BoundsHelper
org.omg.CORBA.TypeCodePackage.BadKindHelper
org.omg.CORBA.ORBPackage.InvalidNameHelper
The IDLtoJava spec clearly specifies the need of the helper class (not the Holder) for these files. But these are absent in the JDK. So, if we try to send any of these classes across in a client-server rmi-iiop model, it will throw an error complaining about the absence of the helper class.
Exact steps to reproduce
1. Write a remote interface with a method that throws any of these 4
exception classes, let it be Invalidname.
eg: public void sayHello( String str) throws java.rmi.RemoteException,InvalidName;
2. Write an impl class for this interface. Also, write an iiop server
which creates an object of this impl class and binds it with
NameService.
3. Write a rmi-iiop client which calls this remote method.
4. Now do an RMIC on the impl class.
Result:
It will throw an error, complaining about the absence of a helper class
for InvalidName.
Expected Result:
RMIC should create stub and tie classes sucessfully.
Exact text of any error messages
_HelloImpl_Tie.java:Undefined variable, class, or package name: org
org.omg.CORBA.ORBPackage.InvalidNameHelper.write(out,ex);
_HelloInterface_Stub.java:Undefined variable, class, or package name: org
if ($_id.equals(org.omg.CORBA.ORBPackage.InvalidNameHelper.id())) {
_HelloInterface_Stub.java:Undefined variable, class, or package name: org
throw org.omg.CORBA.ORBPackage.InvalidNameHelper.read(in);
3 errors
- backported by
-
JDK-2167267 Four helper classes missing in Sun JDK
- Closed
-
JDK-2167268 Four helper classes missing in Sun JDK
- Closed
- duplicates
-
JDK-7130985 Four helper classes missing in Sun JDK
- Closed