It *could* be there's something syntactically wrong with the WSDL and that CXF isn't doing a good job of reporting on the particular error found; you may wish to run Metro's wsimport on your WSDL[1] and see if it either accepts it or is at least more informative about the particular problem (if any) with your WSDL.
Either way, if you could submit a JIRA report with the most minimal WSDL that reproduces the problem CXF can either fix the problem or (if the problem was with the WSDL) can provide a informative error message instead of a stack trace. Glen [1] http://www.jroller.com/gmazza/entry/soap_client_tutorial Dmitry Zinushin wrote: > > Hi, > > I use CXF 2.3 for implement client for external web-service > > wsdl file that ws contains complexType like this (just example for > clarity): > > <xs:complexType name="problem"> > <xs:sequence> > <xs:element name="value" type="xs:string" nillable="true" > minOccurs="0"/> > </xs:sequence> > </xs:complexType> > > When I run wsdl utility for wsdl file with this type I receive error: > > wsdl2java.bat -verbose -client -d .\build\src TestService.wsdl > > Loading FrontEnd jaxws ... > > Loading DataBinding jaxb ... > > wsdl2java -verbose -client -d .\build\src TestService.wsdl > > wsdl2java - Apache CXF 2.3.0 > > WSDLToJava Error: java.lang.reflect.UndeclaredThrowableException > > org.apache.cxf.tools.common.ToolException: > java.lang.reflect.UndeclaredThrowableException > -- View this message in context: http://cxf.547215.n5.nabble.com/wsdl2java-error-tp3265966p3267440.html Sent from the cxf-user mailing list archive at Nabble.com.
