Re^9: SOAP::Lite problem

Actually by looking at the wsdl in more detail, there are a number of functions, amongst them I find "Payment" but each function has a "RequestMsg" and "ResponseMsg" object. I dont know why declaring the wsdl only allows the functions and not further objects. This is and extract of the wsdl...


<xs:element name="PaymentRequestMsg">-<xs:complexType>-<xs:sequence><x
+s:element type="common:RequestHeader" name="RequestHeader"/><xs:eleme
+nt type="account:PaymentRequest" name="PaymentRequest"/></xs:sequence
+></xs:complexType></xs:element>

<wsdl:message name="PaymentRequestMessage"><wsdl:part name="part1" ele
+ment="accountmgrmsg:PaymentRequestMsg"/></wsdl:message>

<wsdl:operation name="Payment"><wsdl:input wsaw:Action="Payment" messa
+ge="account:PaymentRequestMessage"/><wsdl:output wsaw:Action="http://
+www.huawei.com/bme/cbsinterface/cbs/accountmgr/CBSInterfaceAccountMgr
+/PaymentResponse" message="account:PaymentResultMessage"/></wsdl:oper
+ation>
[download]

Comment on Re^9: SOAP::Lite problem Download Code

Replies are listed 'Best First'.
Re^10: SOAP::Lite problem by Anonymous Monk on Oct 20, 2015 at 08:55 UTC
I dont know why declaring the wsdl only allows the functions and not further objects. ;) WSDL is a rabbit hole I dare not interpret on my own, heck, SOAP::Lite can't get it right, so i showed you how to generate what you said was required by avoiding WSDL :)	[reply]
Re^11: SOAP::Lite problem by doqb (Initiate) on Oct 22, 2015 at 00:46 UTC
Totally agreed, I actually took a more coward approached and did the same code on PHP, it worked right out of the box.	[reply]