Closed gallusenrico closed 5 months ago
Thanks for taking the time to fill the issue. For the method rate limit check I've tried to retrieve all beans to get the class. This obviously doesn't work for session scoped beans. I've changed the code get only the class instead of fetching the bean. I've created a 0.12.6-RC1 release. Can you please give it a try? This version should be available in a couple of hours.
I'm sorry. I got a timeout while releasing to nexus. I'll try it later again.
OK, 0.12.6-RC1 should be available soon
Incredible response time! Fix works like a charm for me. Thank you so much
I wanted to check out this really promising looking framework, but unfortunately i stumbled over an issue. I added the following configuration to my application.yaml:
And also needed to add a configuration class and specify some beans in order to make the caching checks pass:
When i started my application, it crashed during the
Bucket4jStartupCheckConfiguration.getRateLimitingAnnotatedClasses
with the following exception:The sessionDataHolder-component that is the reason for the BeanCreationException uses a scope:
@SessionScope
.If i remove the
@SessionScope
definition from the Component, the application boots up without any issues and successfully logs the registration of the filter specified in the application.yaml:INFO 36911 --- [ main] w.Bucket4JAutoConfigurationWebfluxFilter : create-webflux-filter;1;buckets;/login
Adding the
@IgnoreRateLimiting
annotation to the SessionScope class did not prevent the crash.I wanted to write a test for it, but to be honest gave up on trying to make the tests run on my local system. Is there something i can do on my side to prevent this? Please let me know if you need any additional information!