Re: Debugging

Your modification is a great way to make this work for you, so there is no 
reason not to do it.  As you have seen, once you have stripped out the form 
element name, you get text that is a valid SOAP payload.  NuSOAP does not 
require a SOAPAction HTTP header, nor does it require that the Content-Type is 
text/xml (which, technically, it should do), so you are saved from having to 
finagle those.

If the Content-Type contains a charset, it will use that as the character 
encoding, otherwise it assumes UTF-8 encoding.  If you are sending non-ASCII 
characters, this might affect you.

I will look at the ?debug=1 issue later.

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.

----- Original Message ----- 
From: "Chris Boget" <chris@xxxxxxxx>
To: <nusoap-general@xxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, May 12, 2004 12:42 PM
Subject: Re: [Nusoap-general] Debugging


> My comments were based on the assumption that
[snip]
> was a standard SOAP endpoint.  If you have modified it to also
> accept non-standard request formats, more power to you!

I didn't modify it very much.  Aside from one line, it looks *exactly*
like the soap server example on the NuSOAP website:

----------------
  $sXMLString = isset( $HTTP_RAW_POST_DATA ) ? $HTTP_RAW_POST_DATA : '';
  $sXMLString = eregi_replace( 'sXMLString=', '', $sXMLString );

  $server = new soap_server;
  $server->register( 'PolicyInterfaceWebService' );
  $server->service( $sXMLString );
-----------------

That's it.  So if the soap_server shouldn't be able to work with the
data that you are seeing within the textarea of the form then there is
something else going on behind the scenes that I have no hand in.
All I know is that once $sXMLString is passed into my function, it
contains only the XML that is within the "<soap:Body>" node.

But, all of this is tangential to my original problem/question which
was regarding the fact that the debugging information is not being
returned when debugging is turned on.  IE, why does the service
not work when I set "debug=1" (in the query string or in the actual
script) but it does work if I don't initialize the debug variable?
For example, if you just go to

http://eazypro.wild.net/interactive/_WebServices/PolicyInterfaceWebService.php

straight out, you get a soap_server fault with the fault string being:

"error in msg parsing: xml was empty, didn't parse!"

But if you add on the "debug=1" query string

http://eazypro.wild.net/interactive/_WebServices/PolicyInterfaceWebService.php?debug=1

then nothing is returned back to the browser.  Why is that?  Based
on what I've read within the code and based on emails that have
been sent to the list on this subject, the above *should* work.  Yet
it doesn't.

Thank you for your time, assistance and continued patience.

Chris




-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Nusoap-general mailing list
Nusoap-general@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/nusoap-general



-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3