I saw the article on developerWorks: Web Services Programming Tips and Tricks: Use collection types with SOAP and JAX-RPC.
The article discusses how you can get around the problem that "The JAX-RPC specification does not define a mapping for the LinkedList class" (and many other collections).
Then we are lead down the world of a hack, in which we need to use arrays instead of these collections, and how you can use a wrapper to do this.
When we ported the front end of TheServerSide.NET to ASP.NET talking to our business services layer we tried Web Services (as some people wanted us to ;) ).
We ran into this exact problem. We used collections funnily enough, and we had to create a layer in front of our services layer which would just be in charge of converting the collections to arrays..... and back again on the way in.
It gave us a bad taste, and we ended up using Borland Janeva. With Janeva we were able to take our EAR file, feed it to Janeva, and out came C# stubs that we could use directly from our ASP.NET application. That was it. It just worked. I was surprised :)
In our case, we knew that we wouldn't need more types of front ends (e.g. Perl, LISP, .... ) that would want to talk to us, so it made no sense to have a generic layer such as Web Services.
Previous Topic
