I think I'm one strep further. I've discovered that the error occurs
only when I set the priority field during the consumption of the Web
Service.
Their WSDL looks here like this:
<xsd:element name="PRIORITY" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction>
<xsd:simpleType>
<xsd:restriction
base="xsd:string">
<xsd:whiteSpace value="preserve"/
>
</xsd:restriction>
</xsd:simpleType>
<xsd:enumeration value=""/>
<xsd:enumeration value="1"/>
<xsd:enumeration value="2"/>
<xsd:enumeration value="3"/>
<xsd:enumeration value="4"/>
<xsd:enumeration value="5"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
Does this fall within Limitations of ARS?
Well, when I leave the field empty, it's working fine. When I set it
to 1, 2, 3, 4 or 5 I get the error.
I guess I would have to change their WSDL to:
<xsd:element name="PRIORITY" nillable="true" type="xsd:string"
minOccurs="0"/>
the he would let me go, but than I would again have map hundred fields
by hand in the fancy developer studio.
Mark
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
