jlinks

"A new version of a Web service contract that continues to support consumer programs designed to work with the old version is considered backwards-compatible. From a design perspective, this means that the new contract has not changed in such a way that it can impact existing consumer programs that are already using the contract. A simple example of a backwards-compatible change is the addition of a new operation to an existing WSDL definition ..." http://www.infoq.com/resource/articles/Web-Service-Contracts/en/resources/ERL_WSContractVersioning_013613517X_20-22.pdf

Use CXF wsdl2soap .....   (see options) http://cxf.apache.org/docs/wsdl-to-soap.html

"It is quite common for applications to manipulate collections of objects, passing them as arguments to functions and returning them when the processing is complete. There are many ways to represent these collections in most programming languages. They can be expressed as ordered vectors, unordered groups, linked lists, trees, graphs or other forms that the programming language supports. The Java language provides an entire library of collection types in the java.util package. The question, however, is how should you pass collections across a Web services invocation?" http://www.ibm.com/developerworks/webservices/library/ws-tip-coding/index.html