Hoping that enough traffic through here is proficient enough in PHP w/ Webservices to recognize and offer suggestions for the problem I'm having.
I've deployed a webservice server (written natively in Java) that I am hopeful a remote team using PHP will be able to exploit.
I've done my testing from a Java based web service client and it appears to be working fine, i.e., I can accurately generate the client class files by pointing at the WSDL (soap 1.1) and class files are automagically generated, method arguments are properly typed and perform operations on the API exactly as I would have expected.
The remote team is not exactly PHP experts, especially in the context of webservice utilization. They have a couple of examples that they're working from... how hard can it be? However...
Attempts to generate the API information of my webservice in their PHP setup is proving to be a problem. Type information (xsd) doesn't seem to be getting overlaid during the wsdl access process in their PHP application. In examples that seem to work for PHP, xsd:schema information is embedded into the wsdl information in contrast to my wsdl that declares an import of an xsd file within the body of the wsdl file.
Is there supposed to be an interim process that creates a file out of the two, i.e., merging the import of the xsd into the wsdl to create the "real" wsdl for the PHP client to use? Are there libraries that need to be added to the PHP "space" that will do this for them?
Well, maybe it's a bad assumption, and I'll give a look at a tool to double check, but wouldn't it be a good guess that the wsdl is sound if WSDL2Java can properly generate the Java classes from the published wsdl?
I'm covering all exposed functionality that my service provides through a web service client test bed which is why I suspect a missing bit in the PHP code to properly decipher.
BTW, gave Storm a try... thanks for the link, but it simply shows that my service is working as I expected.