You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I create a Spring Data Repository (e.g.: public interface AbcRepository extends PagingAndSortingRepository<Abc, UUID>), and set chaos.monkey.watcher.beans (i.e.: abcRepository), it seems ChaosMonkeyBeanPostProcessor does not wrap the bean properly (the proxy is the same as the original bean according to the debugger).
Expected Behavior
Setting chaos.monkey.watcher.beans on Spring Data's Repository bean should result in wrapping the bean.
Current Behavior
The bean is not wrapped.
Possible Solution
I did not dig that deep, so no idea at the moment.
Steps to Reproduce
I have a reproducer here but chaos-monkey needs to be enabled and chaos.monkey.watcher.beans set.
Context (Environment)
Spring Boot 2.7.0
Temurin-18+36 (build 18+36)
The text was updated successfully, but these errors were encountered:
Might be, please check my minimal reproducer I posted on #317 if I try to assault the repo through the bean it does not work.
I'm able to repro this behavior with the reproducer in #317 and adding chaos.monkey.watcher.beans=helloRepository to the settings.
If I create a Spring Data
Repository
(e.g.:public interface AbcRepository extends PagingAndSortingRepository<Abc, UUID>
), and setchaos.monkey.watcher.beans
(i.e.: abcRepository), it seemsChaosMonkeyBeanPostProcessor
does not wrap the bean properly (the proxy is the same as the original bean according to the debugger).Expected Behavior
Setting
chaos.monkey.watcher.beans
on Spring Data'sRepository
bean should result in wrapping the bean.Current Behavior
The bean is not wrapped.
Possible Solution
I did not dig that deep, so no idea at the moment.
Steps to Reproduce
I have a reproducer here but chaos-monkey needs to be enabled and
chaos.monkey.watcher.beans
set.Context (Environment)
Spring Boot 2.7.0
Temurin-18+36 (build 18+36)
The text was updated successfully, but these errors were encountered: