Comments on: Bloody Web Services :)

By: Larry

Larry — Mon, 28 Mar 2005 19:25:57 +0000

I’ve had similar problems. When I tried to get SOAP attachments working with a .NET client and Axis web service.

Would you use something else if you could decide? At least I would try to use something like Hessian or REST. I’m not a fan of SOAP or Axis. I have not seen a good SOAP web service anywhere. The eBay SOAP API is a good example. They’ve built an SDK on top of it so that it would be easier to use. But it’s still very difficult to use.

By: Ravi

Ravi — Mon, 28 Mar 2005 13:01:42 +0000

Hi Dion,

If you are having issues with the .Net side, the easy solution may be to post this article to Scoble’s blog. He will surely get you a solution :-)
Or better still Don Box !!!
Granted that is not a technical solution but still a solution worth trying, IMHO.

HTH,
Ravi…

By: Robert Nicholson

Robert Nicholson — Sat, 26 Mar 2005 22:16:05 +0000

We are using webservices too and I’ve found that limiting the api to basic types is the best approach. We typically just pass everything as strings xml in xml out. and parse it ourself. As soon as you start messing around with complex types you’re going to have problems.

By: Dan Diephouse

Dan Diephouse — Sat, 26 Mar 2005 19:14:00 +0000

Maybe the decision has already been made, but it looks like you are using rpc/encoded services. The basic profile basically says don’t use rpc/encoded if you want any chance of interop. Really thats where 99% of the interop problems come from. Avoid it and you’ll save yourself a lot of trouble.

And why won’t your MT installation let me post? Its saying that I have “questionable content?”…

By: Ian Lim

Ian Lim — Sat, 26 Mar 2005 08:35:17 +0000

Perhaps you can consider a web service wrapper around an EJB?