Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

TeeJay (2309)

TeeJay
  (email not shown publicly)
http://www.aarontrevena.co.uk/

Working in Truro
Graduate with BSc (Hons) in Computer Systems and Networks
pm : london.pm, bath.pm, devoncornwall.pm
lug : Devon & Cornwall LUG
CPAN : TEEJAY [cpan.org]
irc : TeeJay
skype : hashbangperl
livejournal : hashbangperl [livejournal.com]
flickr :hashbangperl [flickr.com]

Journal of TeeJay (2309)

Friday November 14, 2003
12:39 PM

problems with SOAP::Lite

[ #15773 ]
I thought I would be sensible and not go down the reinventing road to SOAP services so using SOAP::Lite is a no-brainer.

Lots of handy tutorials on the very basic stuff, unfortunately both the API and the Documentation let you down as soon as you reach the nontrivial level.

Even a relatively simple ebXML request becomes a lot of trouble - the basic header and body tags in an ebXML request are more than enough to show that SOAP::Data and SOAP::Header soon become cumbersome.

Fortunately I figured I could wrap that, so I wrote SOAP::Data::Builder which provides a handy wrapper with a nice API to generate complex SOAP requests.

This still leaves me with the problem of how in the world I modify the envelope and body attributes.

Although there is a SOAP::Transport object referred to in the SOAP::Lite perldoc, there is no explaination of what it does or what you can use it for and it has no pod itself.

There doesn't appear to be any way of manipulating the envelope in a client, which just the kind of thing that would make it SOAP::Lite useful.

Despite its claims not to be a crippled API, in its attempts to make SOAP easy for beginners it really holds back any serious work.

I mean why the hell is building a request formed like this so hard :
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
                                   http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd">
  <SOAP:Header xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.x sd"
               xsi:schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-h eader-2_0.xsd
                                   http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">
     <eb:MessageHeader ...>
     </eb:MessageHeader>
  </SOAP:Header>
  <SOAP:Body xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.x sd"
             xsi:schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-h eader-2_0.xsd
                                 http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">
     <eb:Manifest eb:version="2.0"> ... </eb:Manifest>
  </SOAP:Body>
</SOAP:Envelope>

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.