[
https://issues.apache.org/jira/browse/YOKO-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved YOKO-418.
-------------------------------
Resolution: Fixed
Committed revision 632352.
> 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.
