Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re: SOAP::Lite vs LWP::UserAgent for SOAP transactions

by jhourcle (Prior)
on Jul 19, 2006 at 12:44 UTC ( #562272=note: print w/replies, xml ) Need Help??


in reply to SOAP::Lite vs LWP::UserAgent for SOAP transactions

1) When should I use the LWP::UserAgent, and when should I use SOAP::Lite?

Use SOAP::Lite when you want the extra abstraction and less work -- as it supports multiple encodings, it will likely be more forgiving of returned structures should they change schemas. Use LWP::UserAgent when you have special serialization / deserialization needs that can't be met with SOAP::Lite. (which is actually very unlikely, as you can pass alternate serializers / deserializers to a SOAP::Lite object)

2) When using SOAP::Lite, how and when can I build the SOAP content from scratch. What should I use for the SAOP action (In my demo it was the uri with a prefix, but is that the how its done all the time)?

Look through the SOAP::Serializer section of SOAP::Lite. (I've completely overridden the deserialize method in SOAP::Deserializer, but I've never tried doing it with the serializer)

3) What advantages does SOAP::WSDL give me over SOAP::Lite. Is it more recommended?

SOAP::WSDL came along after I started playing with SOAP::Lite, and I never played with it, as it's still listed as an alpha release. I know that the SOAP::Lite has improved its WSDL support since the two came out, but I don't know how the two compare, as I don't use that functionality.

oh -- and you may want to ask your questions on the SOAP::Lite mailing lists, as I don't know how many people on the lists read this site.

  • Comment on Re: SOAP::Lite vs LWP::UserAgent for SOAP transactions

Replies are listed 'Best First'.
Re^2: SOAP::Lite vs LWP::UserAgent for SOAP transactions
by mrguy123 (Hermit) on Jul 19, 2006 at 15:55 UTC
    Thanks for your reply,
    Do you know if there is a way to build the http header using SOAP::Lite?

      You can get the HTTP::Request object that will be used with:

      $soap->transport->http_request()
      and you can manipulate that appropriately.

      However if you simply need to construct a SOAPAction header then that is possible through SOAP::Lite's on_action method.

      /J\

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://562272]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (5)
As of 2022-08-11 17:14 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?