Maybe this was triggered by the fix for my suggestion to actually include the 'description" (error message) in the HTML default representation when ResourceException was thrown?
On Thu, Sep 9, 2010 at 11:24 AM, Tal Liron <[email protected]> wrote: > Just a quick note on changed behavior I noticed in 2.0.1 -- > > If you throw a ResourceException that has a cause, the cause is now sent > to the status service for processing into a new status. If you don't > have explicit support for this, you'll likely get a 500 error, thus > overriding whatever status you set in the ResourceException (say, 404). > I'm not sure if this a regression or intended new behavior... but it did > break a few of my applications. > > -Tal > > On 09/08/2010 12:30 PM, Thierry Boileau wrote: >> Hello all, >> >> The version 2.0.1 of the Restlet framework has been released and can >> be downloaded at this uri: http://www.restlet.org/downloads/. >> The list of bugs fixed and changes is available here: >> http://www.restlet.org/documentation/2.0/jse/changes. >> >> We would like to thank all the people who contributed to this release. >> >> Best regards, >> Thierry Boileau > > ------------------------------------------------------ > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2657215 > -- Fabián Mandelbaum IS Engineer ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2658802
