Thanks Dan,

This leads me to more interesting cases, such as

<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:Enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:a="http://foo.org/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Header>
<a:myHeader SOAP-ENV:actor="http://foo.org/"
xsi:type='xsd:string'>some string</a:myHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<echoStringResponse><str href="#a"/>
</echoStringResponse>
<val Enc:root="0" id="a" xsi:type="xsd:string">Some other string</val>
</SOAP-ENV:Body></SOAP-ENV:Envelope>

So, In this case both myHeader & val are wrong. val can be fixed by
switching it to
<val Enc:root="0" id="a" xsi:type="Enc:string">Some other string</val>

And this particular example of myHeader can be fixed in the same way
<a:myHeader SOAP-ENV:actor="http://foo.org/"
xsi:type='Enc:string'>some string</a:myHeader>

However if myHeader was
<a:myHeader Enc:root='1' SOAP-ENV:actor="http://foo.org/"
xsi:type='Enc:string'>some string</a:myHeader>

Then this requires a new type definition for myHeader, as Enc:string
uses <xs:anyAttribute namespace="##other" processContents="lax" />
dis-allowing the Enc:root attribute as its from the same namespace.

Cheers
Simon
www.pocketsoap.com

On Fri, 22 Feb 2002 18:16:32 -0500, in soap you wrote:

>
>Simon,
>
>It definitely should be xsd1:Document, not xsd:string. It's a bug in the
>serializer code for XMLBus. Thanks for finding it. I've added it to our
>bug queue.
>
>Dan
>
>
>On Friday 22 February 2002 05:55, Simon Fell wrote:
>> I'm checking out some of the current failures, and noticed for
>> compound1 echoDocument I get this response from the Iona endpoint
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <SOAP-ENV:Envelope
>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:xsd1="http://soapinterop.org/xsd"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>> <SOAP-ENV:Body>
>> <xsd1:result_Document ID="1"
>> xsi:type="xsd:string">hello</xsd1:result_Document>
>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
>>
>>
>> My question is does the xsi:type purely apply to the element content
>> [i.e. the string "hello"] or the whole result_Document element ? I
>> thought it was the later, in which case isn't this wrong ? as that
>> definition won't include the ID attribute.
>>
>> Thanks
>> Simon
>> www.pocketsoap.com
>>
>> ------------------------ Yahoo! Groups Sponsor
>> ---------------------~--> Sponsored by VeriSign - The Value of Trust
>> Secure all your Web servers now - with a proven 5-part
>> strategy. The FREE Server Security Guide shows you how.
>> http://us.click.yahoo.com/uCuuSA/VdiDAA/yigFAA/W6uqlB/TM
>> ---------------------------------------------------------------------~-
>>>
>>
>> -----------------------------------------------------------------
>> This group is a forum for builders of SOAP implementations to discuss
>> implementation and interoperability issues. Please stay on-topic.
>>
>> To unsubscribe from this group, send an email to:
>> soapbuilders-unsubscribe@yahoogroups.com
>>
>>
>>
>> Your use of Yahoo! Groups is subject to
>> http://docs.yahoo.com/info/terms/