none
WCF xs:any issue RRS feed

  • Question

  • One of the xsd's we are using in our wsdl has

    xs:any namespace="##other" , processContents="lax"

    We are able to build a service using WCF but when we access the wsdl from

    myservice?wsdl, the "namespace" and processcontents on the xs:any are removed. Since the default value for namespace on "xs:any is "##any" some tools are throwing errors saying the content at "xs:any" is ambiguous.

    Why are "namespace" and processcontents removed from xs:any in the xsd after the service is build?

    Wednesday, March 19, 2014 5:17 AM

Answers

  • Hi,

    I do not know how you are using the xsd in the wsdl, but it should work something like following:

    <xs:complexType name="ExtensibleDocumentedType" abstract="true" mixed="false"> 
          <xs:annotation>
            <xs:documentation>
            This type is extended by component types to allow
            attributes from other namespaces to be added.
            </xs:documentation>
          </xs:annotation>
          <xs:complexContent>
            <xs:extension base="wsdl:DocumentedType">
              <xs:anyAttribute namespace="##other" processContents="lax"/>
            </xs:extension>
          </xs:complexContent>
        </xs:complexType>

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.



    Friday, March 21, 2014 11:26 AM
    Moderator