Has anyone successfully been able to create a web service in remedy (any version) using a custom schema (XSD) and then consume it without using the remedy generated WSDL, but one that includes the same schema used to create the web service? It seems like this should be possible but I am having trouble. The remedy generated WSDL includes both the schema that I used to create the web service and another auto-generated one used as a wrapper. The SOAP requests that remedy is expecting and generating for responses look like this: <?xml version="1.0" ...> <soapenv:Envelope ...> <soapenv:Body> <ns0:OperationResponse xmlns:ns0="urn:PIM_Inbound" xmlns:ns1="http://..."> <ns1:field1>...</ns1:field1> <ns1:field2>...</ns1:field2> <ns1:field3>...</ns1:field3> </ns0:OperationResponse> </soapenv:Body> </soapenv:Envelope>
ns0:OperationResponse is nowhere defined in the schema that I imported. It is from the remedy generated schema and the client errors out when it receives this response becasue it is not expecting it. According to the schema that the client uses (the one I used to create the web service) it should look like this: <?xml version="1.0" ...> <soapenv:Envelope ...> <soapenv:Body> <ns1:field1>...</ns1:field1> <ns1:field2>...</ns1:field2> <ns1:field3>...</ns1:field3> </soapenv:Body> </soapenv:Envelope> Remedy is essentially modifying the schema. I have been able tweak the custom schema to work with the soap request coming in but I can't find a way to prevent remedy from sending the additional OperationResponse element in the response messages. Is there any way to make remedy not modify my schema? -Mike _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

