|
From: Martin A. <sp...@ma...> - 2008-07-08 11:22:16
|
I'll look at that. M On 8 Jul 2008, at 13:11, Ryan J. McDonough wrote: > Martin, > > This sounds similar to the issue I logged: > > http://jira.jboss.com/jira/browse/RESTEASY-63 > > The TestIIOImageProvider.testPostUnsupportedImage() should get a 406 > response with a list of variants rather than a 400. The correct > assertion is currently commented out on line 109. So in addition to > the response code, we also need to include the response information > generated from a WebApplicationException as well. If you're in > there, please have a take a look. > > Ryan- > > > > On Jul 8, 2008, at 5:52 AM, Martin Algesten wrote: > >> >> In ResourceMethod.invoke() line 153, there's a try-catch that makes >> all Failure exceptions thrown below be translated to 400. Is this >> deliberate? To make NumberFormatException result in 404 I want to >> pass >> my error code in the Failure exception, and then get that set in the >> response. >> >> I've checked in a change where we always set the error code passed in >> the Failure - it looks reasonable. >> >> Martin >> >> >> ------------------------------------------------------------------------- >> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! >> Studies have shown that voting for your favorite open source project, >> along with a healthy diet, reduces your potential for chronic >> lameness >> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 >> _______________________________________________ >> Resteasy-developers mailing list >> Res...@li... >> https://lists.sourceforge.net/lists/listinfo/resteasy-developers > |