SOAP::Lite and custom envelopes

[jan]

Hi, I have to create a SOAP client for a third-party webservice. I tried to use SOAP::Lite but my request is not accepted. The support told me how the request has to look like:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envel
+ope/" xmlns:ecom="https://ecomm.sella.it/">
   <soapenv:Header/>
   <soapenv:Body>
      <ecom:Encrypt>
         <ecom:shopLogin>username</ecom:shopLogin>
         <ecom:uicCode>242</ecom:uicCode>
         <ecom:amount>0.01</ecom:amount>
         <ecom:shopTransactionId>562</ecom:shopTransactionId>
      </ecom:Encrypt>
   </soapenv:Body>
</soapenv:Envelope>

However the code produced by SOAP::Lite normally looks like this:

<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" x
+mlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="h
+ttp://www.w3.org/2001/XMLSchema" soap:encodingStyle="http://schemas.x
+mlsoap.org/soap/encoding/" xmlns:soap="http://schemas.xmlsoap.org/soa
+p/envelope/">
      <soap:Body>
          <Encrypt>
              <shopLogin xsi:type="xsd:string">username</shopLogin>
              <uicCode xsi:type="xsd:int">242</uicCode>
              <amount xsi:type="xsd:float">0.01</amount>
              <shopTransactionId xsi:type="xsd:int">562</shopTransacti
+onId>
          </Encrypt>
      </soap:Body>
</soap:Envelope>

So even the envelope tag is different. How can I make SOAP::Lite create a request with the required envelope?

[Anonymous Monk]

I think you need to upgrade SOAP::Lite, see SOAP::Lite and SOAP-ENV and see Re: Suppressing nil attribute in empty SOAP tag

See this treasure trove of SOAP examples and and switch to SOAP::Simple/XML::Compile::SOAP

[sundialsvc4]

Agreed.   It is most likely that a recent version of SOAP::Lite will produce or can be quickly made to produce the desired output.   (It is a very mature package.)   But of course, your only alternative otherwise will be to, “When in Rome, do...”   It never hurts to ask the vendor what Perl package they use, because the chances are excellent that they are using Perl on their side.   I asked that question of Ingram and in a matter of fifteen minutes got an actual code example, sanitized straight from their receiving system that my code would be talking to.   Schweet!

[glasswalk3r]

I agree with the observation, but that just not defeats the usage of a webservice? I mean, if I need to talk with the third party person the implementation details of their webservice, why use SOAP at all? Should the differences in the envelopes have any importance?

I'm saying that because sometime ago I tried to make a SOAP::Lite SOAP service work with a .Net client and it was a real pain to do it.

[jan]

Yes, it is a .Net webservice.

They offer as well a SOAP client written in Java which can be used somehow with Java.pm but we don't want to use Java in our production system.

After unsuccessfully trying to install SOAP::Simple I used the lowlevel way: LWP::UserAgent for the request and pattern matching for the response parsing.

Maybe not the classical way but in this case it was the fastest.

Anyway, thanks for your help, everybody.

[Anonymous Monk]

why use SOAP at all?

Because you're brain damaged :D See REST-vs-SOAP a parable and The REST Dialogs

FWIW, yes, SOAP::Lite is limited, but there are alternatives like SOAP::WSDL and XML::Compile::SOAP::Client/SOAP::Simple