-
Notifications
You must be signed in to change notification settings - Fork 490
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
EZID Service Bean: Modify Logging To include Warnings when processes fail #2277
Comments
Agreed :) |
(This is one of the guidelines for a nicer code style in #775.) |
Actually, I am thinking that when logging into the EZID service fails, this should be logged as |
Change INFO messages to WARNINGs when something went wrong; use log message templates instead of concatenation, and the Throwable variant when a Throwable is passed. Improve formatting, add some javadoc.
Even though I said SEVERE may be better, I gave |
I spoke with @sekmiller about this and he said this issue has become a lower priority for us (post 4.1 for sure) because EZID is doing more now to insulate us from DataCite failures. Or something! He said he's check out the commit by @bencomp at some point. Thanks @bencomp ! |
Change INFO messages to WARNINGs when something went wrong; use log message templates instead of concatenation, and the Throwable variant when a Throwable is passed. Improve formatting, add some javadoc.
When connections to EZID server or create/modify identifier fail, we are only putting INFO into the log not WARNING. We should make them warnings
The text was updated successfully, but these errors were encountered: