CruGlobal/conf-registration-api — pull request #82 by ryancarlson (2013-11-11 23:30:25+00:00)
Title: Undo error handling fixes put in last week and replace with correct handling

It was determined that the reason Chrome was having issues with reporting error messages was that any exception

(NPE for example) was allowed to fall all the way out of the endpoint method. Simply catching any such exception
and wrapping it in a Resteasy ServerErrorException and throwing that will ensure that the proper headers are set
and the correct status code gets back to the client.
- Custom error classes were removed
- Custom `UnauthorizedException` was removed. Resteasy has its own
- All errors (non 2xx) responses are now reported by throwing the appropriate exception
- the exceptions to the above are 502 bad gateway and 41? gone which have no defined exception