On Friday 12 March 2010 7:13:19 pm pdd wrote:
> If wsdl2java works but wsdl2js throws NPE, does it mean there is bug in
> cxf? 

An NPE would definitely be a bug.  Please log it and attach the wsdl/test 
case.  

Dan


> Below is the exception....
> 
> wsdl2js - Apache CXF 2.2.6
> 
> WSDLToJS Error : java.lang.NullPointerException
> 
> org.apache.cxf.tools.common.ToolException: java.lang.NullPointerException
>       at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer
> .java:279) at
> org.apache.cxf.tools.wsdlto.javascript.JavaScriptContainer.execute(JavaScri
> ptContainer.java:151) at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103
> ) at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:67)
>       at
> org.apache.cxf.tools.wsdlto.javascript.WSDLToJavaScript.run(WSDLToJavaScrip
> t.java:60) at
> org.apache.cxf.tools.wsdlto.javascript.WSDLToJavaScript.main(WSDLToJavaScri
> pt.java:97) Caused by: java.lang.NullPointerException
>       at
> org.apache.ws.commons.schema.XmlSchemaCollection.getTypeByQName(XmlSchemaCo
> llection.java:595) at
> org.apache.cxf.common.xmlschema.SchemaCollection.getTypeByQName(SchemaColle
> ction.java:130) at
> org.apache.cxf.javascript.service.ServiceJavascriptBuilder.getElementsForPa
> rts(ServiceJavascriptBuilder.java:746) at
> org.apache.cxf.javascript.service.ServiceJavascriptBuilder.createResponseDe
> serializer(ServiceJavascriptBuilder.java:522) at
> org.apache.cxf.javascript.service.ServiceJavascriptBuilder.end(ServiceJavas
> criptBuilder.java:275) at
> org.apache.cxf.service.ServiceModelVisitor.walk(ServiceModelVisitor.java:76
> ) at
> org.apache.cxf.tools.wsdlto.javascript.WSDLToJavaScriptProcessor.process(WS
> DLToJavaScriptProcessor.java:93) at
> org.apache.cxf.tools.wsdlto.javascript.JavaScriptContainer.execute(JavaScri
> ptContainer.java:144) at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer
> .java:271) ... 5 more

-- 
Daniel Kulp
[email protected]
http://dankulp.com/blog

Reply via email to