[ 
https://issues.apache.org/jira/browse/AXIS2-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Eranga Suriarachchi resolved AXIS2-4489.
----------------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6

Tested codegen with a WSDL which contains custom exceptions and it works and 
compiles without errors. So I'm resolving this issue.

Hari, If you still have any problems with the latest trunk, you can reopen this 
issue and please attach your WSDL for which this issue occurs.

Thanks,
~Isuru

> WSDL2JAVA Compilation errors in the stubs
> -----------------------------------------
>
>                 Key: AXIS2-4489
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4489
>             Project: Axis2
>          Issue Type: Bug
>          Components: client-api
>    Affects Versions: 1.4
>         Environment: Jboss
>            Reporter: hari
>            Assignee: Isuru Eranga Suriarachchi
>            Priority: Critical
>             Fix For: 1.6
>
>
> 1:My service contains operations which throws Exception / User Defined 
> Exceptions.
> 2: When we try to create stubs with the following ant script , we could see 
> compilation errors in the stubs 
>  <target name="wsdl2java">
>         <java classname="org.apache.axis2.wsdl.WSDL2Java" fork="true">
>             <classpath refid="classpath.id"/>
>             <arg value="-ss"/>
>             <arg value="-g"/>
>             <arg value="-uri"/>
>             <arg value="${wsdl.dir}/${wsdl.name}"/>
>             <arg value="-o"/>
>             <arg file="."/>
>         </java>
>   </target>
>  
> 3: For the operations which throws exceptions,we could see duplicate 
> structure defined in the WSDL and type reference is infinite 
>   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to