Re^4: SOAP::Lite server - changing method name in response

I appreciate your effort.:) I ran it (in two instances of course, one server and one client) and got the following result:<bt>

<soap:Envelope soap:encodingStyle="http://schemas.xmlsoap.org/soap/enc
+oding/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:
+soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http:/
+/www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSche
+ma-instance">
  <soap:Header>
    <prod_no xsi:type="xsd:string">two</prod_no>
  </soap:Header>
  <soap:Body>
    <product_info_requestResponse xmlns="http://127.0.0.1/MyModule" xs
+i:nil="true"/>
  </soap:Body>
</soap:Envelope>
[download]

Also, it may be a problem for me using Proc::Background, since the environment that this is going to be used in is quite hard to install new perl modules. But that's a minor.

Comment on Re^4: SOAP::Lite server - changing method name in response Download Code

Replies are listed 'Best First'.
Re^5: SOAP::Lite server - changing method name in response by Anonymous Monk on Aug 24, 2011 at 16:06 UTC
`#~ ->serializer( MySerializer->new ) # WORKS` [download]	[reply] [d/l]
Re^6: SOAP::Lite server - changing method name in response by DreamT (Pilgrim) on Aug 24, 2011 at 16:18 UTC
Thanks...:-)	[reply]
Re^7: SOAP::Lite server - changing method name in response by DreamT (Pilgrim) on Aug 25, 2011 at 10:40 UTC
Another question: When dispatching to a perl sub, it seems like the perl sub needs to return it's values wrapped in SOAP obejcts (i.e. `return (SOAP::Data->name(version=>$IN_artnr)->type('string'));` [download] ) to format it as XML. Is there a way around this, i.e. can the SOAP server itself "fix" this in the response? The purpose is to keep my subroutines "clean", so that their return values work both with SOAP and "ordinary" function calls.	[reply] [d/l]
Re^5: SOAP::Lite server - changing method name in response by DreamT (Pilgrim) on Aug 24, 2011 at 16:00 UTC
(And now when I understood what you were using Proc::Background for, I don't see it as a problem anymore :-) )	[reply]