-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
jce1.2fcs
-
generic
-
generic
Name: stC104175 Date: 04/21/2000
java version "1.2.2"
Classic VM (build Linux_JDK_1.2.2_RC4, native threads, sunwjit)
Several classes in the javax.crypto package and sub-packages are not defined as
Serializable. This makes it impossible to, for instance, communicate
javax.crypto.spec.DHParameterSpec objects with standard RMI calls.
I know for a lot of these objects, there is an encoded format through which one
can communicate (in an architecture independent way), but in the case of
inter-Java VM calls, this is cumbersome.
It should be really up to the service provider implementation to decide if an
object is serializable or not. The way it is specified now, serializability for
some kinds of objects is out of the question.
Anyway, IMHO, there should be a revision of the policy serializability of
objects in these classes.
(Review ID: 103992)
======================================================================
java version "1.2.2"
Classic VM (build Linux_JDK_1.2.2_RC4, native threads, sunwjit)
Several classes in the javax.crypto package and sub-packages are not defined as
Serializable. This makes it impossible to, for instance, communicate
javax.crypto.spec.DHParameterSpec objects with standard RMI calls.
I know for a lot of these objects, there is an encoded format through which one
can communicate (in an architecture independent way), but in the case of
inter-Java VM calls, this is cumbersome.
It should be really up to the service provider implementation to decide if an
object is serializable or not. The way it is specified now, serializability for
some kinds of objects is out of the question.
Anyway, IMHO, there should be a revision of the policy serializability of
objects in these classes.
(Review ID: 103992)
======================================================================