axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Jordahl (JIRA)" <>
Subject [jira] Commented: (AXIS2-665) WSDL2Java generated code does not run correctly
Date Fri, 05 May 2006 13:21:28 GMT
    [ ] 

Tom Jordahl commented on AXIS2-665:

Does Axis2 not automatically support WSDL with multiple ports?
That seems pretty important.  Has anyone run WSDL2Java on the Mappoint WSDL?  It has 4 different
services in it...

> WSDL2Java generated code does not run correctly
> -----------------------------------------------
>          Key: AXIS2-665
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: wsdl
>  Environment: Windows 200 Service Pack 4
>     Reporter: Siim Annuk

> When I generate Java code from a WSDL (using WSDL2Java from Axis2 1.0 RC4) and try to
run (i have created the main method that calls the test functions) the generated test case
(compiling seems successful), I get a java.lang.Error: Unresolved compilation problem: 
> 	Unreachable code.
> When looking into the generated stub code, this is what seems to be generating the problem:
>                                     //Unknown style!! No code is generated
>                                     throw new java.lang.UnsupportedOperationException("Unknown
> Removing it still doesn't run the generated test case correctly. Instead I get a NullPointerException.

> Here's the WSDL I used for testing:
> This is the commandline I use for generating the code: 
> WSDL2Java -uri -t -a -g -u -p stockquote
-o c:\generatedClients\StockQuote
> I have tried to generate the code from many WSDLs at different locations, but never managed
to acutally run any test cases successfully. I've also tried WSDL2Java from Axis2 0.95, 1.0
RC2 and 1.0 RC4.
> Is WSLD2Java still having problems generating correct code from a little bit more complex
WSDL's or am I not using WSDL2Java correctly?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message