Hi Lahiru,
I have few concerns about the former method
* How would you do the first approach for the service method which are
actually returning a boolean value?
*Say we change void to boolean, then a how can the exact exception cab be
passed down to the client since the method may fail due to multiple
exception
* Is it a good practice to change return type just for catching exceptions
On Sun, May 10, 2015 at 10:11 AM, Lahiru Sandaruwan <lahi...@wso2.com>
wrote:
> Hi all,
>
> I have been looking into solving issues in $subject. Found that, currently
> if the back end service method return type is void, service stub throws an
> AxisFault with the message of custom exception message, but not the exact
> exception.
>
> One solution is, to have a boolean return value, for the methods that are
> having return type void, for the purpose of catching custom exceptions.
>
> According to [1], we can throw custom exceptions as below and catch as
> well.
>
> throw new AxisFault(new QName("http://test.org";, "FaultCode", "test"),
> "FaultReason", new Exception("This is a test Exception"));
>
> But i prefer former way as it is crystal clear. Shall we go ahead with
> that?
>
> Wdyt?
>
> [1] http://wso2.com/library/171/
>
> Thanks.
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> phone: +94773325954
> email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
