[RESOLVED] SoapClient testing

NogDog

So I'm starting to build some stuff that will be using PHP's SoapClient to interface with an external system. (By the way, I hate SOAP. 😉 ). I may not have access to an actual SOAP server for awhile. I really don't want to build some sort of SOAP server stub to test my initial code if I don't have to (hey, I'm lazy). Wondered if anyone knew of a relatively easy way to capture what a SoapClient::__doRequest() would actually try to send while not actually sending it?

As I'm writing this up and checking some things in the manual, I see that I could override the method in my local class, so I'm guessing that's where I could do the intercepting, though I'm still too much of a n00b with SoapClient to know yet what I would look at at that point, so any suggestions are welcome.

NogDog

So I'm thinking I could do something along these lines, once I figure out what "magic" to do:

class SyncSoap extends SoapClient
{
	private $debug;

/**
 * Constructor
 * @return void
 * @throws SoapFault if cannot load the WSDL
 */
public function __construct($debug=false)
{
	$this->debug = (bool) $debug;
	$wsdl = realpath(dirname(__FILE__)).'/none_of_your_business.wsdl';
	if(!file_exists($wsdl) or !is_readable($wsdl)) {
		$wsdl = 'http://top.secret.domain.com/none_of_your_business.wsdl';
	}
	parent::SoapClient($this->wsdl);
}

/**
 * Override so we can test without a server
 */
public function __doRequest($request, $location, $action, $version, $one_way = 0)
{
	if($this->debug) {
		// DEBUG MAGIC HAPPENS HERE
	}
	else {
		return parent::__doRequest($request, $location, $action, $version, $one_way = 0);
	}
}

}

NogDog

To continue the discussion with my rubber duck, I'm thinking maybe all I have to do is have my __doRequest() override simply var_dump($this), which I think will get called when I call the desired WSDL function. Maybe I'll find out tomorrow (depending on how long meetings go, what the latest fire is that needs fighting, and so forth 🙂 ).

Weedpacket

If you're just after the XML itself, that's what gets passed in [font=monospace]$request[/font]. Or are you after the HTTP headers as well?

I wondered if there was a way of slapping a stream filter on a given protocol (then you'd be able to stub the whole web server), but no - stream_filter_register only acts on actual streams and all you've got is the URL.

johanafm

__doRequest will be called for by all soap functions you call, and you may have it do whatever you wish. You could mail yourself $request, use curl to post it to a php script, error_log it etc.

Or simply change the value of $location before calling parent::__doRequest which would be another way to log the entire http request, including headers.

NogDog

Well, duh. Note to self: look at the argument list. :rolleyes:

Sounds like a good plan (at least in terms of minimal effort and minimal throw-away code).

Thanks, guys.

NogDog

Just a quick follow-up that the overridden doRequest() stuff worked a treat for me to be able to get things tested without a SOAP server and helped me figure out how to create an additional method to handle the stuff common to all requests. Now it's on to the details and waiting for the test server to become available. Thanks for the help, all.