Use correct resource location for service loader logging of JWTCallerPrincipalFactory #415
Conversation
This file contains 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
sberyozkin
approved these changes
Feb 7, 2021
acoburn
deleted the
feature/service-loader-jwt-caller-principal-factory
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When loading an instance of JWTCallerPrincipalFactory via the
ServiceLoader, that instance will need to be registered under theio.smallrye.jwt.auth.principal.JWTCallerPrincipalFactoryentry in./META-INF/services/.The logging component for this, however, makes use of an incorrect path for that resource. (There is no such
org.eclipse.microprofile.jwt.principal.JWTCallerPrincipalFactoryclass or interface.)