JDK-6375696 : CORBA tie classes for JMX Remote API should be in javax.management.remote.rmi
- Type: Bug
- Component: core-svc
- Sub-Component: javax.management
- Affected Version: 6
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2006-01-23
- Updated: 2017-05-16
- Resolved: 2006-04-14
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6 b81Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Due to bug 6314144, the CORBA tie classes for the remote objects javax.management.remote.rmi.{RMIServer,RMIConnection}Impl were generated in org.omg.stub.javax.management.remote.rmi._{RMIServer,RMIConnection}Impl_Tie instead of javax.management.remote.rmi._{RMIServer,RMIConnection}Impl_Tie as required by the OMG's "IDL to Java Language Mapping Specification". The JDK's ORB looked for these classes in the same place so everything worked. But another ORB implementation that follows the spec to the letter will not find the tie classes.
Now that rmic has been updated so it can generate the tie classes in the right package, the JMX Remote API should be updated correspondingly.
Comments
|