Home/ Questions/Q 320735
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T08:46:52+00:00

I have created a C# .net 2.0 webservice. I need to capture the raw

  • 0

I have created a C# .net 2.0 webservice. I need to capture the raw XML sent from the client and validate it against an XSD and return any errors to the client. The webservice will allow the client to upload a list of widgets to our system.

The following is some background info:

I created an XSD to model a “Widget”, which is a complex object. It looks something like this:

<xs:element name="WidgetList">
    <xs:complexType>
        <xs:sequence>
            <xs:element name="Widget" maxOccurs="unbounded" type="WidgetType" />
        </xs:sequence>
    </xs:complexType>
</xs:element>
<xs:complexType name="WidgetType">
    <xs:sequence maxOccurs="1" minOccurs="1">
        <xs:element name="Seller" type="AccountType" maxOccurs="1" minOccurs="1" />
        <xs:element name="Buyer" type="AccountType" maxOccurs="1" minOccurs="1" />
    </xs:sequence>
    <xs:attribute name="Market" type="MarketType" use="required" />
</xs:complexType>
<!-- etc... -->

Then, I used XSD.exe to generate classes from the xsd.
The Classes that are created are WidgetList, Widget, Seller, Buyer, etc.

Next, I created a webservice method to take the Upload. It looks like so:

[WebMethod]
[SoapHeader("SecurityAuthenticationHeader", Direction = SoapHeaderDirection.In)]
public string UploadWidgets(WidgetList wl)
{
    //Need to validate the XML against the XSD here.

    //Code to import...
}

Two questions:

  1. Is there a way that I can validate the raw XML sent from the client against my original XSD?
  2. Is there anything wrong with the way I have created this service?

UPDATE:
The reason I need to do this is that even though the XSD says fields are required or minOccurs=1, it seems that those properties are not required in the WSDL (Not really sure why).

This is what part of the WSDL looks like (removed unnecessary parts for brevity):

<s:schema elementFormDefault="qualified" targetNamespace="http://www.clearpar.com/XMLSchema">
  <s:element name="lt">
    <s:complexType>
      <s:sequence>
        <s:element minOccurs="0" maxOccurs="unbounded" name="LoanTrade" type="s1:LoanTradeType" /> 
      </s:sequence>
     </s:complexType>
   </s:element>
<s:complexType name="LoanTradeType">
  <s:sequence>
    <s:element minOccurs="0" maxOccurs="1" name="Seller" type="s1:AccountType" /> 
    <s:element minOccurs="0" maxOccurs="1" name="Buyer" type="s1:AccountType" /> 
  </s:sequence>
  <s:attribute name="Market" type="s1:MarketType" use="required" /> 
</s:complexType>
<s:complexType name="AccountType">
  <s:attribute name="Name" type="s:string" /> 
  <s:attribute name="ClientSystemID" type="s:string" /> 
</s:complexType>
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t think that there’s a simple way to do this.

    There is an MSDN article on implementing a SoapExtension to perform schema validation. This is the route I took, with a few enhancements.

    It’s unfortunate that there is no automatic mechanism to validate against the WSDL, especially since the service inherently knows the schema already. I would be interested to know if this situation has changed in WCF: I’m porting my services now and would love it if they’ve solved this problem more elegantly.

    • 0