Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactoring: use Exception mappers instead of try catches in resources. #49

Open
alexnederlof opened this issue Feb 6, 2013 · 0 comments
Milestone

Comments

@alexnederlof
Copy link
Contributor

Currently there's a lot of try/catches in Jersey Resource classes. In general these exceptions should be handled by an Exception mapper. This cleans up a lot of code and should unify our returned HTTP status codes in case of exceptions.

Note: This issue has been automatically migrated from Bitbucket
Created by @michaeldejong on 2012-12-07 20:31:16+00:00, last updated: 2013-01-14 13:41:32+00:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant