Hi Aron, The actual behavior was inconsistent between the constructors with a 'throwable' parameter which were returning the status's description unchanged and others returning the result of Status#toString().
This should be fixed in SVN trunk, to behave as you expected. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : Aron Roberts [mailto:[EMAIL PROTECTED] Envoye : vendredi 24 octobre 2008 01:08 A : [email protected] Objet : ResourceException.getMessage() also returns status description, code? During my first look at the new ResourceException in 1.1RC2, after Jerome added it nearly a year ago :-), it appeared that the values returned by its getMessage() method seemed to always be prefixed by the status description and code. A representative example: Bad Request (400) - Your exception message goes here Since those values ("Bad Request" and "400") are likely to also be individually accessible from the ResourceException - although I haven't yet tried this - via: ResourceException.getStatus().getCode() ResourceException.getStatus().getName() ResourceException.getStatus().toString() and it should therefore be convenient to construct a message with those values, if wanted, my thought is that ResourceException.getMessage() should solely return the underlying or user-provided exception message, without being prefixed by the status description or code. That would increase the number of situations where this message could be used 'as is', without needing to remove the prefix. Since I may be missing something obvious here, I'd welcome thoughts from Jerome and the list ... Aron
