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

should DSAPI top-level exceptions be handled by the DSAPI or Jersey? #36

Open
ehedgehog opened this issue Oct 14, 2014 · 1 comment
Open
Assignees
Labels

Comments

@ehedgehog
Copy link
Contributor

At the moment a thrown exception will go all the way up to the Jersey-controlled endpoints and Jersey will do whatever Jersey does.

We should consider whether we want to intercept all exceptions at the endpoints and generate our own log messages.

@afs
Copy link

afs commented Oct 15, 2014

All exceptions should be caught and logged by the DSAPI and a proper HTTP response sent where possible. Theer is very little reason not to have the top DSAPI level have a try.catch(Throwable) block.

At development time, stacktraces indicate catatrosphic problems and they make log files hard to work with. As currently setup (and maybe that shoudl change) all logging from all deployed Tomcat webapps goes to the same file.

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

No branches or pull requests

3 participants