Schema-compliant message being mangled

Hi 😀

I’m experiencing something strange which I can’t see how to work around. Any input is appreciated.

I have reasonably complex schema split between several files and include`d as appropriate.

I have a BizTalk 2006 orchestration deployed and wrapped by a web service. It accepts a message complying to the schema, makes a slight change to it and returns it to the caller, synchronously.

**********
If I send a schema-compliant message from a client, I can see (using tcpmon) that the incoming SOAP body contains the expected message but the reply (which should be almost exactly the same message) has many elements with missing parameters.
**********

Also, looking at the wsdl generated by BizTalk, it’s clear that it doesn’t match the schema it’s derived-from for the elements that are truncated.

I’m vaguely aware of problems with xsd.exe and wsdl.exe related to using restrictions on complexContent and wonder if BizTalk, internally, has the same issue – thus causing it to be unable to handle my correctly-formatted messages.

(See the end of this post for a snippet of two element definitions, one of which is working as expected).

The xsd.exe issue meant that it’s not been possible to consume a web service using this schema by simply adding a web service reference in the Visual Studio.Net 2005 IDE but instead, I need to manually generate classes from the xsd (currently I’m using XsdObjectGen) to work-around the xsd.exe problems. I’m wondering if there’s some similar approach I might use within BizTalk. I’m new to BizTalk and don’t really understand how it represents the schema internally. It seems to me that there’s a problem mapping the schema to whatever internal representation is used (perhaps a dot net class ?)

Thanks for making it this far 😀

Regards,
Lee.

— Ok ——————————————————————————-
<xs:complexType name=\”Validation\”>
<xs:simpleContent>
<xs:etension base=\”xs:string\”>
<xs:attribute name=\”passed\” type=\”xs:boolean\” use=\”required\” />
</xs:etension>
</xs:simpleContent>
</xs:complexType>

Note: ‘etension’ should be ‘extension’ but the forum forbids me from posting the word 🙁
— Ok (end) ————————————————————————

— Not Ok —————————————————————————
<xs:complexType name=\”Thread\”>
<xs:complexContent mixed=\”false\”>
<xs:restriction base=\”xs:anyType\”>
<xs:attribute name=\”value\” type=\”xs:unsignedInt\” use=\”required\” />
</xs:restriction>
</xs:complexContent>
</xs:complexType>
— Not Ok (end) ——————————————————————–