patch: solve issue with beanpostprocessor not eligable #98
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
rspiegl
changed the title
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.
In the caching module we refactored the conditionals to limit the auto configuration. Due to this the implementation of the CachingConfigurer (to get a custom CacheErrorHandler) needed a dependency on RedisConnectionFactory or else it wouldn't be able to be post processed (due to the CachingConfigurer being needed in a MeterRegistryAutoConfiguration).
This PR limits the dependency on RedisConnectionFactory to the CachingConfigurer and thus makes it easier for Spring to instantiate the beans.