I have fixed this in commit 35a2c1d374b590ae5d9b1822533518ec87371364.
On Fri, Feb 6, 2015 at 4:19 PM, Sajith Kariyawasam wrote:
> I did a remote debug and found that "faultMessage" contains the original
> exception message sent from the backend.
> So if we use
> "e.getFaultMessage().getCartridge
I did a remote debug and found that "faultMessage" contains the original
exception message sent from the backend.
So if we use
"e.getFaultMessage().getCartridgeNotFoundException().getMessage()" it will
display the proper error message.
Thanks,
Sajith
On Fri, Feb 6, 2015 at 11:50 AM, Vishanth Bala
+1 for adding proper error messages
On Fri, Feb 6, 2015 at 11:40 AM, Imesh Gunaratne wrote:
> Yes this problem was identified earlier, we need to fix this. it would be
> better to remove this exception from the get cartridge method and add
> proper error messages.
>
> Thanks
>
> On Fri, Feb 6, 2
Yes this problem was identified earlier, we need to fix this. it would be
better to remove this exception from the get cartridge method and add
proper error messages.
Thanks
On Fri, Feb 6, 2015 at 11:32 AM, Udara Liyanage wrote:
> Hi,
>
> I got the below error logs when I deployed an applicatio
Hi,
I got the below error logs when I deployed an application. I guessed my
application has refered to an non existing cartridge when I saw the
exception CloudControllerServiceCartridgeNotFoundExceptionException since I
know the context. But I feel that this log is not very informative.
1) It have
