JDK-4943189 : (spec) Activatable class should be marked as not serializable
- Type: Bug
- Component: core-libs
- Sub-Component: java.rmi
- Affected Version: 1.4.0
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: solaris_2.6
- CPU: sparc
- Submitted: 2003-10-24
- Updated: 2017-05-16
- Resolved: 2005-03-25
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 betaFixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Name: aaR10142 Date: 10/24/2003 CCC request 4460983 (http://ccc.sfbay/4460983) mentions that java.rmi.activation.Activatable objects should not be serialized/deserialized: " Deserializing an instance of java.rmi.activation.Activatable has never worked in any previous Sun J2SE implementation. Also, doing so is not something that an application should ever have a good reason to do. This flaw in the specification was only detected by the writing of a test for it-- it has never been reported through normal usage. " So, please, add following comments into the class javadoc to point this: /* * ... * serialize a <code>Activatable</code> object will fail. * ... * @serial exclude */ ======================================================================
Comments
|