Thanks Chamila!
On Fri, May 8, 2015 at 8:23 AM, Chamila De Alwis wrote:
> The issue with custom exceptions not being returned was that in the stub
> when recreating the exception, in the returned AxisFault, 'detail' field is
> being set to null. Therefore the custom exception classname cannot be
The issue with custom exceptions not being returned was that in the stub
when recreating the exception, in the returned AxisFault, 'detail' field is
being set to null. Therefore the custom exception classname cannot be
retrieved and only the AxisFault is thrown. I couldn't investigate how the
detai
On Fri, May 8, 2015 at 8:13 AM, Chamila De Alwis wrote:
> +1
> Few notes
>
> 1. Some of Cloud Controller and Autoscaler backend errors are not returned
> as specific custom errors to the stub. Instead they are returned as
> AxisFaults. This needs to be investigated and fixed as an additional
> me
+1
Few notes
1. Some of Cloud Controller and Autoscaler backend errors are not returned
as specific custom errors to the stub. Instead they are returned as
AxisFaults. This needs to be investigated and fixed as an additional
measure. Otherwise the change proposed would not be effective.
2. The CL
Hi all,
It seems $subject is possible. We wrap real exceptions
with UserManagerException in this class. IMO this is not correct way of
handling exceptions.
As a result of this, it returns wrong response.
E.g. Removing non existing user returns "Could not delete user: sd", but it
should return th
