Hi all- We haven't updated yet to 2.0.1, but I'm concerned about this change, as we throw ResourceExceptions with specific status codes fairly frequently in our code, and often also pass a "cause" if we have one, just to give us the option of customizing later. But we don't generally configure the status service. So it sounds like we would also be broken by this change. Would it be possible to always fall back on the original Status code set in the ResourceException?
thanks, Dave Fogel On Thu, Sep 9, 2010 at 10: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 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2663407
