Hello, Well I figured it out. It wasn't that the complex types weren't defined, but the my confusion over similarly named existing and newly defined name spaces that seem arbitrary in some examples and well defined URLs in others. Anyway, because mangle namespaces seem to be the root of most questions I've seen regarding SOAP and to help other newbies in SOAP, WSDL, and WebSerives I'll port my mistake & correction here: In my AmazonServices.wsdl file I had: <wsdl:definitions name="AmazonServices" targetNamespace="http://127.0.0.1/Amazon/AmazonServices.wsdl"; xmlns:tntsoap="http://127.0.0.1/Amazon/AmazonServices.wsdl"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:ns="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:tnt="urn:schemas:tnt"> with needed to be changed to: <wsdl:definitions name="AmazonServices" targetNamespace="http://127.0.0.1/Amazon/AmazonServices"; xmlns:tntsoap="http://127.0.0.1/Amazon/AmazonServices"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:ns="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:tnt="urn:schemas:tnt"> because lower down in the WSDL I defined as the operation endpoint: <wsdl:operation name="AmazonServices"> <soap:operation soapAction="http://127.0.0.1/Amazon/AmazonServices"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> --- targetNamespace="http://127.0.0.1/Amazon/AmazonServices.wsdl"; xmlns:tntsoap="http://127.0.0.1/Amazon/AmazonServices.wsdl"; +++ targetNamespace="http://127.0.0.1/Amazon/AmazonServices"; xmlns:tntsoap="http://127.0.0.1/Amazon/AmazonServices"; I suppose I could have changed the wsdl:operation endpoint to end as in the wsdl:definitions. What I don't like is the the operation endpoint defined pointed nowhere until fixed the wsdl:definitions but the soap client or server didn't complain about not being able to bind to the defined endpoint namespace but then I guess that is cloud computing. Thanks. Regards, Andrew noddle wrote: > > Hello, > > I am trying to write a SOAP client / server app & cannot get the SOAP > message structures passed back and forth between the client & servers: > > Attached are the WSDL, XSDs, XML example, & PHP that is causing me so much > grieve. > > Has anyone any ideal what I am doing wrong? > > I've not attached some of the schemas and skeleton php files. > > This is Mac osX, PHP 5.3 with SOAP extension & apache 2.2.x. > > Thanks. > > http://www.nabble.com/file/p25950961/AmazonServices.wsdl > AmazonServices.wsdl > http://www.nabble.com/file/p25950961/AmazonServicesClient.php > AmazonServicesClient.php > http://www.nabble.com/file/p25950961/AmazonServicesServer.php > AmazonServicesServer.php > http://www.nabble.com/file/p25950961/amzn-envelope.xml amzn-envelope.xml > http://www.nabble.com/file/p25950961/AmazonServices.php AmazonServices.php > http://www.nabble.com/file/p25950961/XMLlibrary.php XMLlibrary.php > http://www.nabble.com/file/p25950961/amzn-envelope.xsd amzn-envelope.xsd > http://www.nabble.com/file/p25950961/amzn-base.xsd amzn-base.xsd > http://www.nabble.com/file/p25950961/amzn-header.xsd amzn-header.xsd > http://www.nabble.com/file/p25950961/FulfillmentCenter.xsd > FulfillmentCenter.xsd > -- View this message in context: http://www.nabble.com/SOAP-message-structure-passing-between-SOAP-client-server-tp25950961p25964818.html Sent from the Php - Soap mailing list archive at Nabble.com. -- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
