[ 
http://issues.apache.org/jira/browse/AXIS2-957?page=comments#action_12437179 ] 
            
William Ferguson commented on AXIS2-957:
----------------------------------------

One final rant from me :-)
IMO it would be better for the Exceptions generated from the WDL for both stub 
and skel to be unbundled from the stub/skel class (ie not generated as static 
inner classes) but created in their own source file. Especially if the "-u" 
option is supplied to Wsdl2Java.  

Bundling them up within the stub/skel just obfuscates the Exception pathway.
And in the case of the stub requires clients to include the stub even if they 
are coding against the stub interface, just to manage the Exception handling.

> AxisServlet does not generate WSDL containing a wsdl:fault
> ----------------------------------------------------------
>
>                 Key: AXIS2-957
>                 URL: http://issues.apache.org/jira/browse/AXIS2-957
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: William Ferguson
>         Assigned To: Deepal Jayasinghe
>            Priority: Blocker
>         Attachments: axis2-957.aar, SimpleService-Source.jar, 
> SimpleService.wsdl, SimpleServiceTest.java
>
>
> I'm using Axis2 1.0 and can't seem to get the AxisServlet to return WSDL that 
> defines a wsdl:fault.
> I have a simple Service class that has 3 methods,
>   1) returns void and throws WSException which extends from Exception
>   2) returns void and throws WSRemoteException which extends from 
> RemoteException
>   3) returns String and throws WSException which extends from Exception
> I package the service up (just the Service class and the Exceptions) with the 
> services.xml and deploy it into Tomcat. I then retrieve the WSDL via the 
> AxisServlet and this is where the problem seems to lie.
> There is no wsdl:fault definitions for any of the service methods that 
> actually throw Exceptions. 
> What do I need to do to get some valid WSDL?
> The second problem is (and this may well be due to the first):
> When I execute a client against this service, the method that returns String 
> throws an AxisFault. Since the WSDL doesn't define any fault I expect this is 
> reasonable. But the other 2 methods don't throw any Exception and just return 
> normally. What has swallowed the Exception?

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to