title: Jersey REST 404 error when there's no path
body: <p>I've got a set of RESTful webservices I've developed, and I'm trying to deal with errors for users in a useful way.</p>
  
  <p>I ran into a situation where I mis-coded the URL for an account resource, and got a 404 error.  I expected an error because there were no @Path annotations in the server that would have responded. But since I got a 404, I reported to the user that their account number was not found.</p>
  
  <p>I guess from a purely RESTful standpoint, 404 "makes sense" because there was no "resource" at /server/foo/123450 (when the correct path to the resource is /server/bar/123450). But /server/thisPathHasNoHopeOfExisting/123450 also responds 404.</p>
  
  <p>/server/bar/000000 where account number 00000 doesn't exist responds 404.</p>
  
  <p>How can I tell my user the right thing? (that /server/thisPathHasNoHopeOfExisting/xxxxxx is a true server error, a 500-series, because the server will NEVER answer to that) -- is there a way to make my Jersey services a bit LESS REST-pedantic?</p>