That soap message looks correct for that situation with cxf 2.1.2. Actually, can you try the latest 2.1.3-SNAPSHOTS? https://issues.apache.org/jira/browse/CXF-1735 may apply here and the client MAY be looking for the person element to be qualified since you did put a namespace on it.
Dan On Wednesday 17 September 2008 10:11:43 am Philipp Schill wrote: > Hi all, > > how can I use java.util.List as a result of a webservice. > > @WebService (targetNamespace="http://www.xyz.com ") > @SOAPBinding(style= SOAPBinding.Style.DOCUMENT, use= > SOAPBinding.Use.LITERAL) public interface MyWebService { > > @WebMethod(action = "lookupPerson") > @WebResult(name = "person", > targetNamespace="http://www.xyz.com/types";) List<Person> > lookupPerson(@WebParam (name = "person") Person person); } > > Person can also be a subclass SpecialPerson. > > The webservice works fine and I get the following SOAPResponse: > > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> > <soap:Body> > <ns2:lookupPersonResponse xmlns:ns2="http://www.xyz.com";> > <person xsi:type="ns2:specialperson" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <name>Philipp</name> > ... > </person> > </ns2:lookupPersonResponse> > </soap:Body> > </soap:Envelope> > > Problem is, that my client doesn't recognize person as element of the list, > so that I can't get access on the attribute name for example. > > Is this a problem of my client or are there any possibilities to do a > better definition by annotations? > > Thanks and regards > phil > > > ________________________________ > The information contained in this communication is confidential, intended > solely for the use of the individual or entity to whom it is addressed and > may be legally privileged and protected by professional secrecy. Access to > this message by anyone else is unauthorized. If you are not the intended > recipient, any disclosure, copying, or distribution of the message, or any > action or omission taken by you in reliance on it is prohibited and may be > unlawful. Please immediately contact the sender if you have received this > message in error. This email does not constitute any commitment from Cordys > Holding BV or any of its subsidiaries except when expressly agreed in a > written agreement between the intended recipient and Cordys Holding BV or > its subsidiaries. Cordys is neither liable for the proper and complete > transmission of the information contained in this communication nor for any > delay in its receipt. Cordys does not guarantee that the integrity of this > communication has been maintained nor that the communication is free of > viruses, interceptions or interference. If you are not the intended > recipient of this communication please return the communication to the > sender and delete and destroy all copies. -- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog -- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
