[ https://jira.jboss.org/jira/browse/JBWS-2529?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2529: ---------------------------------- Summary: Missing type in generated WSDL definition (was: Missing type in generated WSDL part definition) Description: Running CXF java2wsdl tool on a service implementation like this @WebService @SOAPBinding(style=SOAPBinding.Style.DOCUMENT, use=SOAPBinding.Use.LITERAL, parameterStyle=SOAPBinding.ParameterStyle.BARE) public class webParamWebService { ... @WebMethod(operationName="helloString8", action="urn:HelloString8") @SOAPBinding(style=SOAPBinding.Style.DOCUMENT, use=SOAPBinding.Use.LITERAL, parameterStyle=SOAPBinding .ParameterStyle.WRAPPED) public String hello8(@WebParam (name="string8") String name, Address address) { return "hello8 : " + address.getCity() + " to Web Service"; } } seems to cause a wrong wsdl being generated as in the message/part it references elements that are not declared in wsdl/types section. We should reproduce this and see if this is actually a cxf issue or an integration one. was: Running CXF java2wsdl tool on a service implementation like this @WebService @SOAPBinding(style=SOAPBinding.Style.DOCUMENT, use=SOAPBinding.Use.LITERAL, parameterStyle=SOAPBinding.ParameterStyle.BARE) public class webParamWebService { ... @WebMethod(operationName="helloString8", action="urn:HelloString8") @SOAPBinding(style=SOAPBinding.Style.DOCUMENT, use=SOAPBinding.Use.LITERAL, parameterStyle=SOAPBinding .ParameterStyle.WRAPPED) public String hello8(@WebParam (name="string8") String name, Address address) { return "hello8 : " + address.getCity() + " to Web Service"; } } seems to cause a wrong wsdl being generated: ... <wsdl:message name="helloString8"> <wsdl:part name="parameters"> </wsdl:part> </wsdl:message> <wsdl:message name="helloString8Response"> <wsdl:part name="parameters"> </wsdl:part> </wsdl:message> ... The wsdl:part only have name parameter. This is currently preventing the webparam1 reverse test configuration in jws tck5 module, as the obtained wsdl cannot then be consumed by wsdl2java (because it's broken) We should reproduce this and see if this is actually a cxf issue or an integration one. Update title and description as I'm now running with CXF 2.1.4 which seems to behave differently from 2.1.3 (iow it adds the element attribute in the part). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira