Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 70369 invoked from network); 29 Feb 2008 15:07:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Feb 2008 15:07:53 -0000 Received: (qmail 16264 invoked by uid 500); 29 Feb 2008 15:07:47 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 16213 invoked by uid 500); 29 Feb 2008 15:07:46 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 16202 invoked by uid 99); 29 Feb 2008 15:07:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Feb 2008 07:07:46 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Feb 2008 15:07:08 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 265B7234C057 for ; Fri, 29 Feb 2008 07:06:51 -0800 (PST) Message-ID: <1565903724.1204297611156.JavaMail.jira@brutus> Date: Fri, 29 Feb 2008 07:06:51 -0800 (PST) From: "Rick McGuire (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Created: (YOKO-418) Multiple problems marshalling object fields defined as java.util.List MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Multiple problems marshalling object fields defined as java.util.List --------------------------------------------------------------------- Key: YOKO-418 URL: https://issues.apache.org/jira/browse/YOKO-418 Project: Yoko - CORBA Server Issue Type: Bug Security Level: public (Regular issues) Components: orb core, RMI-IIOP Affects Versions: v1.1.0 Reporter: Rick McGuire Assignee: Rick McGuire Fix For: v1.0.0 There are multiple serialization problems showing up when processing serialization using interface classes rather than concrete implementation classes. This problem shows up when a serializable object defines a field using an interface class. For example, this showed up using an object where the field was defined as a java.util.List and a Vector instance was stored in the field. There were multiple bugs that popped out with this scenario: 1) The serialization code was incorrectly treating the List type as an abstract interface rather than a value type, which caused problems on serialization/deserialization. 2) Once this was corrected, problems were found with correctly interpreting fields defined as arrays. 3) Once that was corrected, a problem was encountered with handling chunk boundaries during the deserialization of object arrays. These problems were very difficult to diagnose using the existing logging in the core orb and the RMI support, so some additional logging points should also be added. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.