M
> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
> mailto:dev@cloudstack.apache.org>>
> Cc: Alena Prokharchyk
> mailto:alena.prokharc...@citrix.com>>, Edison
> Su mailto:edison...@citrix.com>>
> Subject: Re: Question regarding Ser
: Wednesday, November 13, 2013 9:46 AM
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>>
Cc: Alena Prokharchyk
mailto:alena.prokharc...@citrix.com>>, Edison Su
mailto:edison...@citrix.com>>
Subject: Re: Question r
Hey Chris,
I think you've got a great point here. It would be nice if
ServerApiException's getMessage() method were overridden to return
getMessage().
I've noticed on occasion, as well, that exceptions I throw out of my
plug-in get caught elsewhere and a more generic (somewhat useless) error
mess
Alena & Edison (or others),
Is there a reason that ServerApiException has a getDescription() method rather
than using getMessage() like all other exceptions? This causes problems in
places where you’d like to treat all exceptions generically and be able to
simply call getMessage(), but ServerAp
