At 2005-02-18, 07:48:51 Peter Mayr <mayr@...
>> You seem to have a mismatch between defining the answer element as
>> array, SOAP-ENC:arrayType="xsd:string", and wanting to see the
>> result as a hash.
>> If you remove the SOAP-ENC:arrayType attribute then S::L will
>> deserialise answer as a blessed hash with the element names source
>Thanks for your reply..
>Unfortunately, since I am writing only the client I have no control
>how the data is sent.. ;-(
>So I guess I have to live with it?
I wonder what the producers of the message mean by having the answer
element defined as an array of strings but each child element having
different element names. To my (simplistic) view this seems
i.e. why do the dc:source and dc:format elements have different names
if they are meant to be simply entries of an array?
Really, the element names should not be significant, rather their
position in the sequence is what is significant.
However you might be able to get around this by writing a custom
deserialiser for the AnswerElement type, but I cannot see any examples
of how to do that.
ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com