Easy answer to SOAP problems: IBM Datapower SOA Appliance. http://www-03.ibm.com/software/products/us/en/datapower/ I played with this one: http://www-03.ibm.com/software/products/us/en/datapower-xi50 Current stuff is http://article.wn.com/view/2013/04/29/SOA_Software_Enables_REST_Services_on_... Short version: you shell out EUR 250K + IBM consulting fees and this translates whatever SOAP you want into something readable and it does it fast. Note: this is one of the hottest selling products of IBM at the moment, they ship it by the boatload to banks and organisations requiring heavy security/regulations. Putting Pharo behind this makes for a pretty good solution. Phil On Mon, Jun 3, 2013 at 7:31 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 03 Jun 2013, at 18:08, Norbert Hartl <norbert@hartl.name> wrote:
In order to use SOAP properly you need a full namespace aware xml parser, a xml schema parser, a WSDL parser plus code generator and the will to abuse HTTP completely . Even if you build a perfect tool you'll maybe face the not so perfect responses from the remote side.
Even using the Java stack with all its tools and frameworks, SOAP is still terrible. Especially if you have to interface with Microsofts' idea of SOAP and web services.
But Johan implied already that it would not be fun.
On the other hand, I think that XML Support _is_ namespace aware. So it would not be too hard to actually generate/parse SOAP messages for real. You could get already pretty far with that, IMHO.
Sven
PS: In another life I did http://common-lisp.net/project/cl-soap/ - it was never perfect but it kind of worked to talk to Google AdWords.
-- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill