SOAP has no standard support for any collection apart from arrays. As prevoius posters have said breaking the SOAP compatibility is generally a bad idea (surely compatibility, not hype, is the reason you are using WS)
The varying set serialisation is a bit of a worry, but understandable since (I hope) the first priority for axis is SOAP interop. There are two ways you could bypass the set serialisation problem (or some combinaiton of the two): 1) Define a net set of types that use arrays instead of collections, and add methods to your existing types that convert between the two. 2) Add custom serialisers & deserialisers to you endpoints - this way you can use arrays "on the wire" but in you code deal only with you collection types 3) I know I said two, but that becuase this one is a bad idea - use java's built in XML bean serialiser and add the XML inline or as a soap attachment. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841008#3841008 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841008 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
