Issue 4283: RMI repository ID references to serial version UID (interop) Source: Oracle (Mr. Everett Anderson, ) Nature: Uncategorized Issue Severity: Summary: CORBA formal 00-11-03 10.6.2 states "If the actual serialization version UID for the Java class differs from the hash code, a colon and the actual serialization version UID (transcribed as a 16 digit upper-case hex string) shall be appended to the RepositoryId after the hash code." Please comment on the following assertions. The CORBA spec is vague here, and it has resulted in incompatible interpretations which must be resolved quickly. 1) The "actual serialization version UID" mentioned is as defined in the Java Object Serialization specification. http://java.sun.com/j2se/1.3/docs/guide/serialization/spec/class.doc6.html#4100 Based on this Java specification and its note that "If the SUID is not declared for a class, the value defaults to the hash for that class": 2) If a serialVersionUID field is defined in the class with the proper modifiers, its value is used as the "actual serialization version UID" mentioned in the CORBA spec 3) If a serialVersionUID field with the proper modifiers is not explicitly defined in a class, its value is computed as explained in the Java Object Serialization spec, and this computed value is used as the "actual serialization version UID" mentioned in the CORBA spec 4) It is required by the CORBA spec to always include the Java serialVersionUID (as computed in assertions 2 and 3 above) in the RMI repository ID if the value is different than the OMG hash code (for which the algorithm is defined in CORBA formal 00-11-03 10.6.2) 5) It is not acceptable to leave off the SUID portion of the RMI repository ID if the serialVersionUID field is merely absent from the Java class Resolution: closed, withdrawn by submitter Revised Text: Actions taken: April 25, 2001: received issue May 18, 2001: closed issue Discussion: End of Annotations:===== Date: Wed, 25 Apr 2001 13:27:51 -0700 From: Everett Anderson X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf,ja MIME-Version: 1.0 To: issues@omg.org, interop@omg.org Subject: RMI repository ID references to serial version UID Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: #[)!!m[>!!5%d!!_&Vd9 Hi, I have another request for clarifications about the RMI repository ID: CORBA formal 00-11-03 10.6.2 states "If the actual serialization version UID for the Java class differs from the hash code, a colon and the actual serialization version UID (transcribed as a 16 digit upper-case hex string) shall be appended to the RepositoryId after the hash code." Please comment on the following assertions. The CORBA spec is vague here, and it has resulted in incompatible interpretations which must be resolved quickly. 1) The "actual serialization version UID" mentioned is as defined in the Java Object Serialization specification. http://java.sun.com/j2se/1.3/docs/guide/serialization/spec/class.doc6.html#4100 Based on this Java specification and its note that "If the SUID is not declared for a class, the value defaults to the hash for that class": 2) If a serialVersionUID field is defined in the class with the proper modifiers, its value is used as the "actual serialization version UID" mentioned in the CORBA spec 3) If a serialVersionUID field with the proper modifiers is not explicitly defined in a class, its value is computed as explained in the Java Object Serialization spec, and this computed value is used as the "actual serialization version UID" mentioned in the CORBA spec 4) It is required by the CORBA spec to always include the Java serialVersionUID (as computed in assertions 2 and 3 above) in the RMI repository ID if the value is different than the OMG hash code (for which the algorithm is defined in CORBA formal 00-11-03 10.6.2) 5) It is not acceptable to leave off the SUID portion of the RMI repository ID if the serialVersionUID field is merely absent from the Java class Thank you, Everett Date: Wed, 25 Apr 2001 22:01:34 +0100 From: Simon Nash Organization: IBM X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I) X-Accept-Language: en MIME-Version: 1.0 To: Everett Anderson CC: interop@omg.org Subject: Re: RMI repository ID references to serial version UID References: <3AE73347.3E48DD78@sun.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: cSdd9C^P!!SZ*e9#_"e9 Everett, I agree with all your assertions. Simon Everett Anderson wrote: > > Hi, > > I have another request for clarifications about the RMI repository ID: > > CORBA formal 00-11-03 10.6.2 states > > "If the actual serialization version UID for the Java class differs from > the hash code, a colon and the actual serialization version UID > (transcribed as a 16 digit upper-case hex string) shall be appended to > the RepositoryId after the hash code." > > Please comment on the following assertions. The CORBA spec is vague > here, and it has resulted in incompatible interpretations which must be > resolved quickly. > > 1) The "actual serialization version UID" mentioned is as defined in > the Java Object Serialization specification. > > http://java.sun.com/j2se/1.3/docs/guide/serialization/spec/class.doc6.html#4100 > > Based on this Java specification and its note that "If the SUID is not > declared for a class, the value defaults to the hash for that class": > > 2) If a serialVersionUID field is defined in the class with the proper > modifiers, its value is used as the "actual serialization version UID" > mentioned in the CORBA spec > > 3) If a serialVersionUID field with the proper modifiers is not > explicitly defined in a class, its value is computed as explained in the > Java Object Serialization spec, and this computed value is used as the > "actual serialization version UID" mentioned in the CORBA spec > > 4) It is required by the CORBA spec to always include the Java > serialVersionUID (as computed in assertions 2 and 3 above) in the RMI > repository ID if the value is different than the OMG hash code (for > which the algorithm is defined in CORBA formal 00-11-03 10.6.2) > > 5) It is not acceptable to leave off the SUID portion of the RMI > repository ID if the serialVersionUID field is merely absent from the > Java class > > Thank you, > Everett -- Simon C Nash, Chief Technical Officer, IBM Java Technology Tel. +44-1962-815156 Fax +44-1962-818999 Hursley, England Internet: nash@hursley.ibm.com Lotus Notes: Simon Nash@ibmgb