axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derek Foster (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-931) WSDL2Java generated fault exceptions don't provide a way to specify an exception message or cause.
Date Thu, 17 Aug 2006 19:29:14 GMT
    [ http://issues.apache.org/jira/browse/AXIS2-931?page=comments#action_12428766 ] 
            
Derek Foster commented on AXIS2-931:
------------------------------------

There is a copy of my WSDL in AXIS2-928. I think that pretty much any WSDL that uses faults
should exhibit this problem, though.

> WSDL2Java generated fault exceptions don't provide a way to specify an exception message
or cause.
> --------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-931
>                 URL: http://issues.apache.org/jira/browse/AXIS2-931
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: databinding
>            Reporter: Derek Foster
>            Priority: Blocker
>
> When WSDL2Java is run for the latest nightly build, generating XMLBeans code,  the exception
classes that are being generated for WSDL faults do not have any declared constructors. As
a result, it is impossible to specify any kind of message (for debugging purposes, etc.) except
by using the setFaultMessage method.
> The currently generated code looks like this:
>     /**
>      *  FServiceSkeletonInterface java skeleton interface for the axisService
>      */
>     public interface FServiceSkeletonInterface {
>      
> 		 
>         /**
>          * Auto generated method signature
>          */
>         public  crc.Fimport.xmlbeans.wsdl.ReturnDocument acceptFEvent
>         (
>           crc.Fimport.xmlbeans.F.FullEventUpdateDocument param4     
>          )
>          
>            throws crc.Fimport.wsdl2java.FServiceSkeletonInterface.FailureException;
>      
>          public static class FailureException extends java.rmi.RemoteException{
>             private crc.Fimport.xmlbeans.wsdl.FailureDocument faultMessage;
>             public void setFaultMessage(crc.Fimport.xmlbeans.wsdl.FailureDocument msg){
>                faultMessage = msg;
>             }
>             public crc.Fimport.xmlbeans.wsdl.FailureDocument getFaultMessage(){
>                return faultMessage;
>             }
>          }
>    
>          }
> However, I think that at a minimum, two additional constructors should be provided to
class FailureException:
> FailureException(String message)
> {
>    super(message);
> }
> FailureException(String message, Throwable cause)
> {
>   super(message, cause);
> }

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message