Thanks for your answer ,
Don't know how to do that but I will find out soon. Worth to try it .
Because IMHO , when apache soap receives an object that has the following
structure :
<theobj type="SOAP-ENC:Array" arrayType="anyType[10]" >
<item>
...
</theobj>
apache soap should try to deserialize it as a Vector and not try to convert
to an array (the arrayType is anyType, so can't be an array) .
As I see things, using the apache way to send a Vector ( with their own
namespace ) could be avoided by doing this kind of encoding. For me, this
seems more acording to the specs.
But , as I say, I am not an expert ...
:o)
Thanks again
dovle .
> You could change the mapping in the soap registry but that would be a bad
> idea.
>
> If interoperability with non-apache soap is important have found that the
> best thing to do is simplify the service interface to use arrays and not
> use Java collection classes.
>
> Robert
>
