I posted this CXF bug (https://issues.apache.org/jira/browse/CXF-5061) in JIRA but it hasn't received many comments so I thought I'd send out a message to the mailing list. Attached to the issue are the files to reproduce the bug. CXF is generating an invalid WSDL when returning a List of complex objects (non-primitive). In my example I created a simple object called WrapperString that is an Object with a String field. Whenever CXF creates the WSDL, there is a complexType named "wrapperStringArray" yet the getListResponse is trying to use the type of "ns0:WrapperStringArray". The bug is that the capitalization of the types do not match. I think the getListResponse type should be a lowercase "w". I ran another test with a List<String> and the types were correctly generated to "stringArray". It seems like CXF is messing the capitalization of the type when using complex objects. This is quite a high priority issue so I can get SOAP services to work correctly with a valid WSDL.
-- View this message in context: http://cxf.547215.n5.nabble.com/Invalid-WSDL-generated-for-List-of-Complex-Type-tp5729239.html Sent from the cxf-user mailing list archive at Nabble.com.
