An invalid SOAP fault would not cause a SAXParseException. I suspect that's also a SimpleSOAP problem. If you're looking for a simple C/C++ SOAP engine, I recommend gSOAP (http://www.cs.fsu.edu/~engelen/soap.html) or Axis C++ (http://ws.apache.org/axis/cpp/index.html).
Anne On Jan 11, 2008 5:27 PM, Andrew Wood <[EMAIL PROTECTED]> wrote: > Thanks Anne, Alastair & Andreas > > Thats what I wasnt sure - whether the problem was being caused by > Axis or SimpleSOAP. If Axis is behaving correctly I'll take this to > the SimpleSOAP forum on Sourceforge and see if the SimpleSOAP > creators can help me track down what its doing wrong. > > > If the error response is invalid is that the cause of the Axis client > throwing a SAXParseException saying 'Content is not allowed in the > trailing section' then? > > Regards > > Andrew > > > > On 11 Jan 2008, at 22:17, Anne Thomas Manes wrote: > > > My guess is that your SimpleSOAP framework is at fault. > > > > 1- the error your received in response is not valid. The <faultcode> > > and <faultstring> elements in the fault response message should not be > > namespace qualified. > > 2- the SOAP message generated by Axis is formatted correctly. (Note, > > though, that the <getString> element should be namespace qualified. > > The namespace URI comes from the @namespace attribute in the > > <soap:Body> description in the WSDL.) > > > > Perhaps your framework is looking explicitly for the "SOAP-ENV" > > namespace prefix -- but that's an inappropriate constraint. the prefix > > string is not relevant. A string like "foo" is equally valid, e.g., > > > > <?xml version="1.0" encoding="UTF-8"?> > > <foo:Envelope xmlns:foo="http://schemas.xmlsoap.org/soap/envelope/"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > <foo:Body> > > <getString soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/ > > encoding/"> > > <name xsi:type="xsd:string">Andrew</name> > > </getString> > > </foo:Body> > > </foo:Envelope> > > > > Anne > > > > On Jan 11, 2008 3:26 PM, Andrew Wood <[EMAIL PROTECTED]> wrote: > >> Hi > >> > >> The server, which I've wrote myself, uses the C++ based SimpleSOAP > >> framework. It may be a fault with the server but I cant see what > >> it may be. > >> > >> This is the complete SOAP sent by Axis to call a method getString, > >> which > >> takes a single string parameter on an object called Test.. to me > >> it looks > >> perfectly OK.. > >> > >> > >> POST /Test HTTP/1.0 > >> Content-Type: text/xml; charset=utf-8 > >> Accept: application/soap+xml, application/dime, multipart/related, > >> text/* > >> User-Agent: Axis/1.4 > >> Host: 10.0.1.4:2000 > >> Cache-Control: no-cache > >> Pragma: no-cache > >> SOAPAction: "" > >> Content-Length: 385 > >> > >> > >> <?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> > >> <getString > >> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> > >> <name xsi:type="xsd:string">Andrew</name> > >> </getString> > >> </soapenv:Body> > >> </soapenv:Envelope> > >> > >> > >> > >> Regards > >> Andrew > >> > >> > >> > >> > >> > >> On 11 Jan 2008, at 19:52, Andreas Veithen wrote: > >> > >> > >> @Andrew: The value of the namespace prefix (soapenv or SOAP-ENV) > >> indeed > >> doesn't matter. The only thing that is relevant is the namespace > >> URI it is > >> bound to (http://schemas.xmlsoap.org/soap/envelope/). Do you have > >> any idea > >> what Web service framework the server uses? > >> > >> Regards, > >> > >> Andreas > >> > >> > >> On 11 Jan 2008, at 20:39, Alastair FETTES wrote: > >> > >> > >> Hi Andrew. > >> > >> Theoretically soapenv should be perfectly acceptable. > >> Irregardless of > >> what the prefix is, as long as the actual namespace is the same it > >> should recognize things appropriately. > >> > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > ______________________________________________________________________ > > This email has been scanned by the MessageLabs Email Security System. > > For more information please visit http://www.messagelabs.com/email > > ______________________________________________________________________ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
