This repository was archived by the owner on Oct 12, 2020. It is now read-only.
Error handling for debugging #32
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Error handling tweaks
Recently was trying to use plugin on Keycloak (6.x), some minor tweaks that came out of it:
Try catch in ContentTypeHelper
Changed the try cache exception - maybe because of using older version of keycloak? Or some classpath issues, as on my instance there was org.jboss.resteasy.spi.BadRequestException instead of javax.ws.rs.BadRequestException. Changed to general Exception as it really doesn´t matter why recognition failed.
Logging general exception in ValidateEndpoint
Previous error was not easily debugged without it, as the exception was not logged properly. Had another issues with missing jaxb on classpath that needed to be properly logged as well. If something unexpected happens, it should be logged and at least some UUID of error added.