[ 
http://issues.apache.org/jira/browse/AXIS-2195?page=comments#action_12323066 ] 

David Wong commented on AXIS-2195:
----------------------------------

I think we can just catch the RemoteException and rethrow it as an AxisFault.  
Thanks for the help.  I think you can close this issue now.  However, I am 
still curious as to why the original behavior is 1.1 has changed.

> WSDL2Java generates a org.xmlsoap.schemas.wsdl.soap.TFault object that is not 
> a Throwable.
> ------------------------------------------------------------------------------------------
>
>          Key: AXIS-2195
>          URL: http://issues.apache.org/jira/browse/AXIS-2195
>      Project: Apache Axis
>         Type: Bug
>     Versions: 1.2.1
>  Environment: Windows XP, "Apache Axis 1.2.1 Final ChangeLog (Changes after 
> 1.2 Final)"
>     Reporter: David Wong
>  Attachments: AgencyIntegrationServices-V1.0.wsdl, src.zip
>
> I am also having compilation problems with version 1.2 wsdl2java generated 
> code. Wsdl2java generates a soap binding impl class that has methods which 
> throw a org.xmlsoap.schemas.wsdl.soap.TFault object. The TFault object 
> generated has the following inheritance heirarchy:
> java.io.Serializable
>         |
>         org.xmlsoap.schemas.wsdl.TExtensibilityElement
>                   |
>                   org.xmlsoap.schemas.wsdl.soap.TBody
>                            |
>                            org.xmlsoap.schemas.wsdl.soap.TFaultRes
>                                    |
>                                    org.xmlsoap.schemas.wsdl.soap.TFault
> Since this heirarchy does not include a Throwable, the compiler will error 
> out and tell you that you are trying to throw something that is not 
> throwable. The WSDL that I am using works with Axis 1.1 and in that version, 
> TFaultRes is inherited from AxisFault which is a RemoteException. I am 
> attaching the WSDL file I used (AgencyIntegrationServices-V1.0.wsdl) to this 
> issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to