axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Sauthier (JIRA)" <>
Subject [jira] Commented: (AXIS-1838) Array deserialization
Date Tue, 15 Mar 2005 22:04:33 GMT
     [ ]
Guillaume Sauthier commented on AXIS-1838:

Maybe something :

It seems that we're not using maxOccurs attributes in serilalization process; if we have a
maxOccurs="unbounded" for a given Type, I think it should be serialized as an Array.
That's not the case now.

Is this a wanted behavior ?

I have made changes in my sandbox, seems to resolve this Array problem (at least partially;
last some errors with xsd:base64Binary "array"). TCK tests are running. I will let you know
if I found something else.

> Array deserialization
> ---------------------
>          Key: AXIS-1838
>          URL:
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     Versions: 1.2RC3
>  Environment: JOnAS 4.3.3
>     Reporter: Guillaume Sauthier
>     Assignee: Glen Daniels
>  Attachments: axis-array-deser-error-patch.txt
> When running TCK for JOnAS, sometimes, I fall on array deserialization issue :
> The SOAP Message contains 3 elements of the array, but the constructed array only has
the last element. So its size is 1, instead of 3!
> The problem only occurs when using Array with Helper :
> ArrayofBook
> -> Book[] arrayOfBook
> +
> ArrayOfBook_Helper
> I'll attach a patch for test.holders that reproduce this problem.
> failures will appear for testInOutBookArray

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message