The problem is with server own SoapFaults and my SoapFaults... It s possible for me not to send SoapFault in my daemon... The typical problem is a query error... handle() never give me the hand... I use ob_start() to catch the soap response to redirect it on the client socket. It work fine... But if a soap fault is send, my code is never executed... and the soapfault is printed on stdout!!!
so... I need to catch soapFault events...
regards
Charles FENDT
>Hi Fendt, > >Do you mean SoapFaults you generate with your PHP script (ie. You throw them >yourself, to create a soapfault response) or does the SOAPServer throws his >own soapFault (ie invalid request or something simillar)? > >Regards, > >David > > >>> -----Original Message----- >>> From: FENDT Charles [mailto:cfendt@silicom.fr] >>> Sent: Wednesday, February 23, 2005 5:35 PM >>> To: soap@lists.php.net >>> Subject: Re: SV: SoapServer & SoapFault >>> >>> The server is prety easy... >>> (I don't have many clients...) >>> I use a stream_socket_server... and just the POST methode... >>> I read the POST data and give them to handle... >>> >>> I try to provide a remote telnet access (TN5250 client) with >>> HTML pages... >>> The pre alpha script work fine, but the server side has to >>> keep the telnet connexion why the AS400 ! >>> If i use an Apache server, a script will lunched at each >>> query, and killed after each response. >>> So, it's impossible to me to use this architecture... >>> So, I need a deamon, and to improve interoperability, i want >>> to use SOAP transaction. >>> => the server has to keep running even if a soapfault is throw!!! >>> >>> So => HELP!!!! >>> >>> A simple empty query kill my server !!! :-( >>> >>> I need to catch this !!!! >>> >>> FENDT Charles >>> >>> >>> >>> Danne Lundqvist a écrit : >> >>> > It sounds a bit weird to create a SOAP server as a command >> >> line script >> >>> > as it needs a web server to get the request. >>> > The SOAP server only handles the actual soap request. It does not >>> > handle the communication. >>> > >>> > Mabye it could be done ofcourse if you implemented your own > >> transport > >>> > communication but I don't know how/if that would work. >>> > >>> > Either way. A soap server without a webserver (or another > >> server that > >>> > handles the communication) sounds a bit weird. >>> > >>> > /Danne >>> > >>> > >>> > -----Ursprungligt meddelande----- >>> > Från: FENDT Charles [mailto:cfendt@silicom.fr] >>> > Skickat: den 23 februari 2005 16:47 >>> > Till: soap@lists.php.net >>> > Ämne: SoapServer & SoapFault >>> > >>> > >>> > hello >>> > Is it possible to catch SoapFault exception during > >> SoapServer::handle() ??? > >>> > >>> > handle does not return any exception... >>> > I didn't found any documentation about SoapServer error... >>> > I didn't found any doc about use_soap_error_handler()... does is >>> > answer to my question? how? >>> > >>> > please, help... >>> > >>> > I need to implement a Soap Daemon (command line script)... so, the >>> > script must continue to be executed, even if an error occured in on >>> > request... >>> > (actualy, the first SoapFault stopes my daemon :-( ) >>> > >>> > Charles FENDT >>> > > >> >> -- >> PHP Soap Mailing List (http://www.php.net/) To unsubscribe, >> visit: http://www.php.net/unsub.php >> >>
-- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
