Month: June 2004

It turns out that the change to RPC style was exactly what made the difference. Now the Java client can call into my .NET web service without a problem. Specifically,…

I have switched from “message” style to “RPC” style encoding of the WSDL in response to advice on the MSDN web site: http://msdn.microsoft.com/library/en-us/dnservice/html/service12052001.asp. Apparently Java uses RPC more frequently. Maybe…

I tried this: <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <StartEvaluation xmlns="http://ottawa.byu.edu/Emar" href="#id0" > </StartEvaluation> <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="" xsi:type="ns1:StartEvaluation" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://ottawa.byu.edu/Emar"> <PIN xsi:type="xsd:string">TESTPIN</PIN> <QuestionnaireName xsi:type="xsd:string">READY</QuestionnaireName> </multiRef> </soapenv:Body> </soapenv:Envelope>…

I came across a very handy, easy to compile Java application that makes it easy to just paste in and modify SOAP requests and analyze the web service responses. It…

I got it to work, with modification. Here’s a snippet of what the client was trying: <StartEvaluation xmlns="http://ottawa.byu.edu/Emar"> <parameters href="#id0" xmlns=""/> </StartEvaluation> <multiRef id="id0" ...> <PIN xsi:type="xsd:string">TESTPIN</PIN> <QuestionnaireName xsi:type="xsd:string">READY</QuestionnaireName> </multiRef>…

Tried to get a Java client using webMethods to communicate with my .NET web service. I was not on the Java end. A 3rd party client was. We had an…