Re: Apache SOAP and interop

From: Dale Green <>
Date: Wed, 24 Apr 2002 09:35:34 -0700

Hi Arun,

Since Collections will be supported, does this mean that all of the
implementation classes (ArrayList, LinkedList, HashMap, etc.) will
be supported in JAX-RPC FCS?

The 0.8 version of the JAX-RPC specs does not mention Collections
in the section on supported Java types. Does this mean that our
support of Collections is implementation-specific?



>User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4)
Gecko/20020314 Netscape6/6.2.1
>X-Accept-Language: en-us
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>Date: Wed, 24 Apr 2002 08:33:16 -0700
>From: Arun Gupta <>
>Subject: Re: [JAX-RPC] Apache SOAP and interop
>Comments: To: "Peter C. Tribble" <>
>Hi Peter,
>Thanks a lot for your valuable comments on interoperability. Collections
>and Hashtable will be supported in the upcoming release of JAX-RPC in
>June 2002.
>Thanks for your interest in JAX-RPC.
>Peter C. Tribble wrote:
>>>>>Has anyone tried using a non java client with apache SOAP or
>>>>>JAXRPC as yet ?
>>>>>I tried using a M$ client with JAXRPC and it didnt quite work
>>>>>for a simple example...i ll try again to see what the problem was....
>>>>>Has anyone had success with the Apache (not Axis) implementation ?
>>I've been using Apache soap, Axis, JAX-RPC under java. SOAP::LITE under
>>perl, and have used Tclsoap and a couple of python implementations.
>>Usually it's Apache soap or SOAP::LITE on the server side, and they both
>>work well (and interoperate well) on the client side. All the other things
>>work well on the client side for what I'm doing, except JAX-RPC (which
>>doesn't handle Collections out of the box, and almost everything I pass
>>is either a List or a Hash). I've been very pleased with the level of
>>interoperability in general.
>>-Peter Tribble
>>HGMP Computing Services
>There is only one me, I must live myself!
>There is only one today, I must live itself!