Does anyone know how to log all request and responses with the builtin SoapClient in PHP? I could in fact manually log everything with SoapClient::__getLastRequest()
and SoapClient::__getLastResponse()
But we have that much soap requests in our system that i'm looking other possibilities.
Note: i'm using wsdl mode so using a method that tunnels all through to SoapClient::__soapCall()
isn't an option
I think the better way is to override
SoapClient::__doRequest()
(and notSoapClient::__soapCall()
) as you'll have direct access to the request- as well as to the response-XML. But the general approach to subclassSoapClient
should be the way to go.EDIT
From an OOP-design / design pattern point of view a Decorator is obviously the better way to handle this kind of problem - please see Gordon's answer. But this is a little bit more difficult to implement.
Adressing the issue raised in https://stackoverflow.com/a/3939077/861788 I came with the following solution (full source):
Usage:
SOAP client will then log every request and response using any PSR-3 logger.
I second Aleksanders and Stefans suggestion but would not subclass SoapClient. Instead I'd wrap the regular SoapClient in a decorator, because logging is not a direct concern of the SoapClient. In addition, the loose coupling lets you easily substitute the SoapClient with a mock in your UnitTests, so you can concentrate on testing the logging functionality. If you only want to log specific calls, you can add some logic that filters requests and responses by $action or anything you see fit.
Edit since Stefan suggested to add some code, the decorator would probably look something like this, although I am not sure about the __call() method (see Stefans comments)
Sorry to revisit such an old post, but I encountered some challenges with the accepted answer's implementation of a decorator that is responsible for the logging of the Soap requests and wanted to share in case anyone else runs into this.
Imagine you set up your instance like the following, using the SoapClientLogger class outlined in the accepted answer.
Presumably any method you call on the SoapClientLogger instance will get passed through the __call() method and executed on the SoapClient. However, typically you make use of a SoapClient by calling the methods generated from the WSDL, like this:
This usage will never hit the SoapClientLogger's _doRequest() method and thus the request will not be logged. Instead AddMember() is routed through $mySoapClient::_call() and then right on down to the SoapClient instance's _doRequest method.
I'm still searching for an elegant solution to this.
Would something like this work?
Since SoapClient already sends all requests through __soapCall, you can intercept them by subclassing SoapClient and overriding it. Of course, to make it work you need to also replace every
new SoapClient(...)
in your code withnew MySoapClient(...)
, but that seems like a pretty easy search and replace task.