From: gregarican <greg.kujawa@...>
Date: 2006-11-21T04:40:06+09:00
Subject: Re: Soap project. RubyCLR vs Jruby vs Soap4r?

Soap4r is a nice package for working with SOAP in Ruby. I used it for
creating a client app that automatically pulls precious metal commodity
pricing and then it turn updates an internal app's retail pricing
formulas. You are right on target, in that if your client app will
require cookies you will have to use http-access2 rather than basic
net/http. I haven't used other services such as .Net, Perl, Python for
building SOAP client apps but I can't imagine that they would be as
clean, concise, and elegant as Ruby. But then again I might be biased
since Ruby is my language of choice ;-)

snacktime wrote:
> So I have a couple of weeks to write an application that will
> integrate with a soap based web service.  Unfortunately I have some
> challenges and very little experience with soap, although I can
> probably figure things out ok once I decide which platform I'm going
> to use, which is where  I'm at now.  Also, I'd much prefer to do this
> in linux/bsd if I can, with windows as a last option.
>
> First I tried using wsdl2ruby on the supplied wsdl file which didn't
> work.  Not surprising, but that means if I use soap4r I'm going to
> have to do everything from scratch, and I'm really not sure what that
> all entails.  One other thing, the soap client has to support cookies,
> as the server uses 3 cookies for session management once
> authentication is done.  I saw one http-access2 comment about using
> cookies on the net, but that was it.
>
> Then I took a look at using .net.  There is rubyclr which appears to
> work only on windows and not with mono.  Ironpython which doesn't have
> most of the standard python library, and python.net which works fine
> on windows but has issues on linux with mono.
>
> Finally I'm looking at jruby and using it with something like apache
> axis, which the webservice vendor say's is known to work.  I've pretty
> much ruled this one out as I'm not a java guru and I really hate using
> those bloated apache frameworks.
>
> And I also took a look at soaplite in perl.  Not a bad option IMO and
> it's around second on my list right now after soap4r.
> 
> Any comments or suggestions?