This post originated from an RSS feed registered with Java Buzz by dion. Original Post: Bloody Web Services :) Feed Title: techno.blog(Dion) Feed URL: http://feeds.feedburner.com/dion Feed Description: blogging about life the universe and everything tech Latest Java Buzz Posts Latest Java Buzz Posts by dion Latest Posts From techno.blog(Dion)

Yup, a project that I am working on is having a bad time with Web services. The core problem is that interop is just not there.

Because of this, if I am a Web services consumer, I am going to:

Always give out a simple API set of stubs in various languages

As a user of a current Web services provider, I just want to have some bloody stubs which wrap their services and make sure all works well. The current stubs are Axis 1.1-ish, and are not working right.

Why not? due to multiRef. .NET Server doesn't like multiRef too much (for simple types). When you make a call the .NET Server says something like this right?:

Error: Cannot understand multiref at line 3, element foo

Er no. We get back:

SOAP Error

NO INFORMATION. Fun to debug for sure. "Hmm, let me try this... or this... or this.."

So, I have to learn from this experience and if I am ever a consumer:

• Give decent error messages back to my users
• Have good documentation on the common problems
• Have a lot of sample code showing the services working
• Have an API that users can download which has been TESTED

Shoot, I would much rather be talking to some damn EJBs! :)

Grr...

proxySoap._getProperty(Call.OPERATION_STYLE_PROPERTY): ERROR