From: "M. Edward (Ed) Borasky" Date: 2006-11-20T09:58:39+09:00 Subject: Re: Soap project. RubyCLR vs Jruby vs Soap4r? 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. Hmmm ... you have very little experience with SOAP, yet you've accepted an assignment/made a commitment to use it to "write an application that will integrate with a soap based web service" in "a couple of weeks". Does anyone on this list have a non-technical comment on the situation here? :) > 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? 1. Take a deep breath 2. Write down what the application *must* do, and *when*. 3. Pick a technology that you *know* will accomplish that. Pick the *simplest* thing that can do the job. 4. Get it done! 5. Come back here and tell us all how you did it, even if it had nothing to do with Ruby. :) Good luck ... and stay agile. :) -- M. Edward (Ed) Borasky, FBG, AB, PTA, PGS, MS, MNLP, NST, ACMC(P) http://borasky-research.blogspot.com/ If God had meant for carrots to be eaten cooked, He would have given rabbits fire.