JDK-5021246 : Spec for RMI connector should say code downloading used if applicable
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-03-26
  • 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.
JDK 6
6 b81Fixed
Description
The RMI connector uses the "default class loader" to load deserialized classes in the client, in accordance with the general specification for connector clients.  But, for JRMP, it will also use code downloading if that is enabled and the default class loader does not find a class.  This is a natural consequence of the RMI implementation and corresponds to what people want.  So the spec should explicitly say that this is what happens.

Comments
PUBLIC COMMENTS .
04-09-2004

EVALUATION Changing the Javadoc for javax.management.remote.rmi should suffice here. ###@###.### 2004-03-26
26-03-2004