Issue 4286: Clarification of serialization of Anys and Typecodes (java-rtf) Source: IONA (Mr. John Cosgrove, ) Nature: Clarification Severity: Summary: I have a request for clarification of the IDL to Java language mapping concerning the serialization of Anys and Typecodes. Both classes implement IDLEntity and so would be expected to be serializable. Is this the intention of the mapping? I would also expect that TCKind should also implement IDLEntity and have a readResolve() method as suggested in the recent discussions of Issue 1752 revising the mapping for enums. Is this correct? Resolution: see below Revised Text: Incoporate revised text for section 1.4.1.3, Fix the incorrect java code in section 1.19.9, update the OMG.zip file (including adding the missing TCKindHelper and TCKindHolder classes), and close the issue. Revised Text: Add the following bullet to the end of the bullet list in section 1.4.1.3: - Any class that implements IDLEntity Actions taken: April 26, 2001: received issue May 13, 2002: closed issue Discussion: Any class that implements IDLEntity must be serializable. However, the spec does not explicitly say this. It should be updated in section 1.4.1.3 to clarify this. The resolution to issue 4271 adds a readResolve method to all enum classes. Looking at the current spec, TCKind is defined to be an enum. but the java code in the spec does not include IDLEntity. End of Annotations:===== Reply-To: From: "jcosgrove" To: Subject: Clarification of serialization of Anys and Typecodes Date: Thu, 26 Apr 2001 15:09:29 +0100 Message-ID: <008401c0ce5a$83890f30$4903020a@cosgrove.dublin.iona.ie> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Importance: Normal Content-Type: text/plain; charset="iso-8859-1" X-UIDL: ],&e9EY+!!8&@e9Gp[d9 Hello all, I have a request for clarification of the IDL to Java language mapping concerning the serialization of Anys and Typecodes. Both classes implement IDLEntity and so would be expected to be serializable. Is this the intention of the mapping? I would also expect that TCKind should also implement IDLEntity and have a readResolve() method as suggested in the recent discussions of Issue 1752 revising the mapping for enums. Is this correct? regards John Cosgrove