I updated to the latest nightly snapshot this morning, and now see the
following error emitted from wsdl2java.sh when passing it a WSDL 2
description, specifying either "-wv 2" or "-wv 2.0" on the command
line.

,----
| Woden[Fatal Error],0:0,WSDL501,Expected a 
"{http://www.w3.org/ns/wsdl}description"; element, but found a 
"{http://www.w3.org/2006/01/wsdl}description"; element instead.
| Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
|         at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerationEngine.java:142)
|         at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
|         at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
| Caused by: WSDLException: faultCode=INVALID_WSDL: Fatal WSDL error:
| 0:0,WSDL501,Expected a "{http://www.w3.org/ns/wsdl}description"; element, but 
found a "{http://www.w3.org/2006/01/wsdl}description"; element instead.:
|         at 
org.apache.woden.internal.ErrorReporterImpl.reportError(ErrorReporterImpl.java:229)
|         at 
org.apache.woden.internal.ErrorReporterImpl.reportError(ErrorReporterImpl.java:184)
|         at 
org.apache.woden.internal.ErrorReporterImpl.reportError(ErrorReporterImpl.java:169)
|         at 
org.apache.woden.internal.BaseWSDLReader.parseDescription(BaseWSDLReader.java:355)
|         at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:202)
|         at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:233)
|         at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:246)
|         at 
org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:121)
|         at 
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.<init>(WSDL20ToAxisServiceBuilder.java:134)
|         at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerationEngine.java:89)
|         ... 2 more
`----

This same command-line invocation was working fine with yesterday's
snapshot build, so something must have changed that's preventing the
proper WSDL 2 namespace from being used.

Should I file a JIRA issue?

-- 
Steven E. Harris


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to