I'm not convinced that the Apache containers are the de facto standard. Both WASP and GLUE use .NET-compatible containers by default, although they also support Apache-compatible containers. (I haven't checked, but I suspect that BEA, Cape Clear, and XMLBus support .NET-compatible containers by default also.)
See: http://www.systinet.com/doc/wasp_jserver/messageProcessing/serializationFram ework.html#messageProcessing.serializationFramework.javaCollections http://www.themindelectric.com/docs/glue/guide/mapping/collections.html Anne > -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED]] > Sent: Friday, November 22, 2002 1:48 PM > To: [EMAIL PROTECTED] > Subject: Re: Document style web services > > > > ----- Original Message ----- > From: "Anne Thomas Manes" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, November 22, 2002 10:14 AM > Subject: RE: Document style web services > > > > From what I've seen, most vendors have designed containers that are > > compatible with .NET. Perhaps Axis should do the same. > > > Are we talking about data types like List and HashTable? I dont think .NET > puts them on the wire: no serializer, see. > > Its actually the Apache SAOP containers that are the de-facto standard... >
