[ 
https://issues.apache.org/jira/browse/AXIS2-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Boris Georgiev reopened AXIS2-3341:
-----------------------------------


Rich,

For Reference: neither Sun's JAX-WS RI, nor Websphere's Webservices Option Pack 
(which uses Axis2 as webservice engine) works this way.

Referring to the same JAXB 2.0 5.5.2 (not 5.2.2) quote: "A collection property 
may take the form of an indexed property or a list property". The word used is 
may, not must. The specification says nothing about the array properties, which 
by default are to be treated as simple properties. I have used JAXB up to day 
on objects, containing only list properties on their collections. JAXB always 
handled them correctly and never complained that it needs an indexed property. 
And serializing an object's handle in an XML document does not make any sense, 
as it becomes completely meaningless, outside the JVM

> Marshaling arrays and lists seems to be wrong
> ---------------------------------------------
>
>                 Key: AXIS2-3341
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3341
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>    Affects Versions: 1.3, 1.2
>         Environment: JDK 1.5 and Geronimo 1.1 , also Websphere 6.1
>            Reporter: Boris Georgiev
>            Assignee: Rich Scheuerle
>         Attachments: jaxws-axis2.zip, return_messages.txt
>
>
> The problem seems to be about incorrect marshaling of arrays and lists. Looks 
> like, for each element in the array is called the method toString(), then all 
> of the array elements are separated by spaces and finally all the result is 
> placed in a single xml element.
> As I see, according to the schema in the WSDL, every element of the array 
> needs to be in its own element. Then, calling toString() may work for a 
> simple type, it is completely meaningless for a complex types, as it is 
> usually the string representation of the object's handle.
>  
> I get the same result with or without response wrapper objects. I observe it 
> for the return types, I have not tested it for arrays in the input 
> paparameters.
> Can I use some other databinding mechanism, in order to avoid this and how?
> To demonstarate it, I have created a simple web service project. The service 
> name is "GenericService" there are four methods, returning: array of string, 
> array of a complex type, list of string and a list of a complex type.
> The attached file return_messages.txt contains the messages: as they are 
> observed and as they need to be for arrays. For lists, the messages are the 
> same.
> Te attached file jaxw-axis2.zip contains the sample geronimo/eclipse project, 
> without the axis2 libraries.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to