On Thursday 01 July 2010 9:49:50 pm nbhatia wrote: > I just realized that for the simplified example in my last post, the return > type generated is indeed a List. It is only when OrderCriteria becomes more > complex (includes a list of enumerations etc.) that the generator starts > wrapping the List return type. Don't know if there is any workaround for > this. > > Thanks. > Naresh
You would need to make sure both the request and response object meet the requirements defined in the jaxws spec: (section 2.3.1.2) (i) The operation’s input and output messages (if present) each contain only a single part (ii) The input message part refers to a global element declaration whose localname is equal to the operation name (iii) The output message (if present) part refers to a global element declaration (iv) The elements referred to by the input and output message (if present) parts (henceforth referred to as wrapper elements) are both complex types defined using the xsd:sequence compositor (v) The wrapper elements only contain child elements, they MUST not contain other structures such as wildcards (element or attribute), xsd:choice, substitution groups (element references are not permitted) or attributes; furthermore, they MUST not be nillable. -- Daniel Kulp [email protected] http://dankulp.com/blog
