Great observation! It makes sense to me that the component types of a List object should always be considered as an Object. The code should not look at the actual data to determine the type. (The elements of the List could be missing, mixed or null).
This is one of those situations where the serialization runtime does not
have enough information to serialize the object.
In this case, the javaType and the xmlType are both needed. Since the
current Axis runtime does not know the expected
xmlType, it makes some big assumptions!
I will run some experiments to see if any tests break.
Any other comments?
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Vikram Rayabhari
<vikram@yasutech. To: [EMAIL PROTECTED]
com> cc:
Subject: Array Serializer and
java.util.List
02/27/2002 07:34
AM
Please respond to
axis-user
Hi,
There seems to be a bug in ArraySerilizer when a list containing objects
of different classes is serialized. The arrayType attribute is being set
to the type of the first element in the list and not to xsd:anyType as
would be expected.
Could someone please clarify?
thanks
Vikram
