WCF request with default empty tags

Question

I'm trying to connect to a SOAP 1.1 webservice, using TLS. The certificate has been set up right, and I am able to communicate with the webservice.

However, when I try to do this using a plain C# project, using proxyclasses generated by VS2010, the request seems to be incomplete, as in, the empty tags are not in the request. I then get a "This is an operation implementation generated fault" fault, viewable in Fiddler

If I then try to launch a request using SoapUI, I get a succesful response from the webservice.

I used Fiddler to compare both requests, and I noticed that the C# request was pretty plain, only sending elements that were filled in in my C# class. But when I check the SoapUI request, this request included EVERY element defined in the WSDL/XSD's, even though they're empty.

I'm trying to understand how I can configure the C# client to include empty elements, to see if the webservice will accept my request, however I was unable to find such setting.

The C# request response:



  
    
      
        SOAP-ENV:Server
      
      
        This is an operation implementation generated fault
      
      
      
        
          2.0
          XML schema validation error
          
            /{urn:xxx:xxx:service:contractcancellation:1:standard}ContractCancellationRequestEnvelope[1]/part1[1]/ContractCancellationRequestEnvelope[1]/BusinessDocumentHeader[1]/Destination[1]

The C# request:

POST xx HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: "urn:ContractCancellationRequestEnvelope"
Host: xx
Content-Length: 887
Expect: 100-continue
Accept-Encoding: gzip, deflate
Connection: Keep-Alive


  
    
      
        
          xxx
          
            
              2013-11-15
            
          
          
            xxx
            
              TST0000001

The SoapUI request:

As you can see, the SoapUI request is far more complete, even though the elements are empty.

C# code (important parts):

_binding = new BasicHttpBinding(BasicHttpSecurityMode.Transport);
_binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;

_endpoint = new EndpointAddress(endpointAddress + "xxx");

_proxy = new ContractCancellationPortTypeClient(_binding, _endpoint);
_proxy.ClientCredentials.ClientCertificate.SetCertificate(
       StoreLocation.LocalMachine,
       StoreName.My,
       X509FindType.FindBySubjectName,
       "xxx");
_proxy.ContractCancellation(new ContractCancellationRequestEnvelope()
       { Portaal_Content = new ContractCancellationRequestEnvelope_PC()
           { Portaal_MeteringPoint = new ContractCancellationRequestEnvelope_PC_PMP()
               { EANID = request.EanId,
                 MPCommercialCharacteristics = new ContractCancellationRequestEnvelope_PC_PMP_MPCC()
                   { ContractCancellationDate = request.ContractCancellationDate },
                 Portaal_Mutation = new ContractCancellationRequestEnvelope_PC_PMP_PM()
                   { Initiator = request.SupplierEanId,
                     Dossier = new ContractCancellationRequestEnvelope_PC_PMP_PM_Dossier()
                       { ID = "TST0000001" }
                   }
               }
           });

Tim · Accepted Answer

In your code, you're generating the Portaal_Content portion of the ContractCancellationRequestEnvelope, but not the BusinessDocumentHeader portion.

If you look at the fault received (via C#) I'm betting that there's one or more required elements in the BusinessDocumentHeader section that are missing:

The error text is XML schema validation error, and the error detail is:

ContractCancellationRequestEnvelope[1]/part1[1]/ContractCancellationRequestEnvelope[1]/BusinessDocumentHeader[1]/Destination[1]

You need to ensure that all required elements are present in your SOAP message.

EDIT

Something like this should do the trick:

ContractCancellationRequestEnvelope reqMsg = new ContractCancellationRequestEnvelope();

reqMsg.BusinessDocumentHeader = new BusinessDocumentHeader()
    { CorrelationTimestamp = "?",
      MessageID = "?" };
reqMsg.BusinessDocumentHeader.Destination = new Destination();
reqMsg.BusinessDocumentHeader.Receiver = new Receiver()
    { ReceiverID = "?" };

And so on. Basically, make sure that you create every element that is required.

By the way, you can do nested automatic initialization (as in the code you posted), I simply took a more explicit route in my example for readability.

The service's WSDL will tell you what is required or optional.

If you need more help either provide the URL for the service or post the WSDL.

WCF request with default empty tags

Answers (1)

Related Questions