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 ]

lilstevey (4628)

lilstevey
  (email not shown publicly)

Consumes:
  • Heinekin
  • Kro
  • Addlestones
  • Old Rosie
  • Thatchers
  • Strongbow
  • Erdinger
  • Guiness
  • Budvar
  • Leffe ( usually blond )
  • Various Real Ales when in premises suitable

Journal of lilstevey (4628)

Wednesday March 29, 2006
06:02 AM

Perl Soap to Java Soap

[ #29148 ]
And still the mission goes on. Having produced a prototype, that proved that using a java soap client to talk to a perl backend seems to work quite well for CRUD style operations, its now time to start tightening down the screws.

Axis seemed a lot more supported than apache soap, so first thoughts were moving the codebase onto there, and its looking quite promising.
After doing a little reading, it seems that document-literal services seem to be a better fit:

Although soap::lite seems a little cludgey for non-rpc stuff - any one know of something or a technique that would let me build a response from a stream of SAX events?

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.
  • I justed ditched SOAP::Lite in favour of some custom-written, specialised code (for MMS-handling). I'm basically using Template::Toolkit to generate SOAP requests, and various XML-tools to handle SOAP requests (plus LWP, MIME, etc).

    It's just so much easier to satisfy various very picky SOAP-servers by issuing handcrafted requests that just work, than to suffer the never-ending agony caused by SOAP::Lite.

    • Thanks for your thoughts. I've had some mixed experiences with SOAP::Lite. It did really really help me at first, and the learning curve for it ( at least for perl -> perl comms ) was good. it worked reasoanbly well when I started using it for java2perl too, although a little a little kruft started appearing around the edges.

      But as I demand more of it the intuitiveness of the interface seems to go down significantly.
  • I used SOAP::Lite::Simple to connect to the FTC's Do Not Call service. It lets you write your SOAP messages by hand but takes care of lots of the boring details for you.