Well, it's definitely not the same error as CXF-2054 as the testcase added for CXF-2054 does pass with 2.3.1. Thus, it's something new.
Is there any way you can send along the wsdl/schemas? I can then take a quick look to see what is happening. It's trying to find the individual part from the wrapper, but failing which means there is a qname mixup or something. I'm not really sure what would cause that so a quick test case would be good. Dan On Thursday 16 December 2010 1:27:07 pm Pieper, Aaron wrote: > After upgrading CXF from 2.3.0 to 2.3.1, I get a NullPointerException > building stubs for my project: > > org.apache.cxf.tools.common.ToolException: > java.lang.NullPointerException > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContai > ner.java:279) > at > org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java: > 103) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86) > at > org.apache.cxf.maven_plugin.WSDL2JavaMojo.callWsdl2Java(WSDL2JavaMojo.ja > va:410) > ... 22 more > Caused by: java.lang.NullPointerException > at > org.apache.cxf.tools.wsdlto.frontend.jaxws.validator.WrapperStyleNameCol > lisionValidator.mapElementName(WrapperStyleNameCollisionValidator.java:1 > 62) > at > org.apache.cxf.tools.wsdlto.frontend.jaxws.validator.WrapperStyleNameCol > lisionValidator.isValidOperation(WrapperStyleNameCollisionValidator.java > > :115) > > This looks the same as https://issues.apache.org/jira/browse/CXF-2054, > and http://cxf.547215.n5.nabble.com/wsdl2java-NullPointer-td560285.html. > Is it possible this bug was reintroduced in CXF 2.3.1? > > - Aaron -- Daniel Kulp [email protected] http://dankulp.com/blog
