Thanks for your prompt answer, James. "james.clover" wrote : Java Collection classes aren't recommended for SOAP interfaces, mostly for interop reasons. If all you're needing is a list of objects without duplicates, then your interface can just be an array of objects. You can treat is as a Set from either side of the interface.
I am afraid I cannot change my domain objects to always use arrays instead of Sets. I am using Hibernate as my persistence layer, and Hibernate demands that properties mapped as arrays or Lists strictly obey the list semantics, i.e. be indexed. What's more, it requires a table column holding the index of each array element, and changing the table layout is simply no option. On the other hand, I am operating in a homogenous java environment, so interop concerns are a non-issue. So do I have other options? Cheers, Olaf <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827296#3827296";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827296>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
