Hi,
I'm experiencing a problem with SOAP that people usually wouldn't run into.
I've mailed Dmitry about this, but have so far received no reply (he's
usually pretty fast, but I am aware that he's had little time the past few
days). I'm anxcious to know if the problem might be resolved in PHP 5.0.1
though, because it's really causing problems in my development. Is there a
changelog for the CVS versions somewhere that I could look into maybe?
For the people interested about my problem (which I'm not sure should be
called a bug), I'll try to explain it shortly:
When using a SOAP server in a CLI environment, returning a SoapFault
automatically stops the whole script, which is very unwanted behavior. The
client script should stop, but not my soap server. It seems perfectly normal
to me that throw'ing the SoapFault would cause the serverscript to stop, but
I think that returning it should be the non-fatal solution to this.
Thank you,
Ron
update: Dmitry contacted me, he will look into it.
"Ron Korving" r.korving@xit.nl wrote in message
news:20040811092618.49773.qmail@pb1.pair.com...
Hi,
I'm experiencing a problem with SOAP that people usually wouldn't run
into.
I've mailed Dmitry about this, but have so far received no reply (he's
usually pretty fast, but I am aware that he's had little time the past few
days). I'm anxcious to know if the problem might be resolved in PHP 5.0.1
though, because it's really causing problems in my development. Is there a
changelog for the CVS versions somewhere that I could look into maybe?For the people interested about my problem (which I'm not sure should be
called a bug), I'll try to explain it shortly:When using a SOAP server in a CLI environment, returning a SoapFault
automatically stops the whole script, which is very unwanted behavior. The
client script should stop, but not my soap server. It seems perfectly
normal
to me that throw'ing the SoapFault would cause the serverscript to stop,
but
I think that returning it should be the non-fatal solution to this.Thank you,
Ron