Sorry about incremental updates, but I think it's important for me to say that the WSDL XSD looks okay.
The full SOAP message that Drools server sends is like this: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns1:executeResponse xmlns:ns1="http://soap.jax.drools.org/";> <ns1:return></ns1:return> </ns1:executeResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Notice the "return" element that contains the CDATA chunk that contains the message contents. That matches the WSDL XSD. It *seems* that .NET is trying to apply the WSDL XSD to the CDATA chunk. So instead of recognizing one "return" element (which is actually in the message) it sees an XML chunk containing a "result" element and a "fact-handle" element but no "return" element. Perhaps we can fix it by changing the data contract(s) for the response. Dunno. But the WSDL XSD seems to match the actual message. Clark -- View this message in context: http://drools.46999.n3.nabble.com/rules-users-NET-WCF-unable-to-deserialize-response-from-Drools-Camel-Server-example-6-2-0-snapshot-tp4030566p4030600.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
