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
2024-05-28T11:26:03.392+08:00 WARN 74763 --- [state-machine] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.statemachine.config.configuration.StateMachineAnnotationPostProcessorConfiguration' of type [org.springframework.statemachine.config.configuration.StateMachineAnnotationPostProcessorConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). The currently created BeanPostProcessor [org.springframework.statemachine.processor.stateMachineAnnotationPostProcessor] is declared through a non-static factory method on that class; consider declaring it as static instead.
SpringBoot considers StateMachineAnnotationPostProcessor as a PostProcessor. The creation of this bean necessitates the prior instantiation of the StateMachineAnnotationPostProcessorConfiguration class. However, the instantiation of this class further requires all PostProcessors to process it, including StateMachineAnnotationPostProcessor. Consequently, this results in a warning log indicating that some PostProcessors cannot process it. While it's true that the StateMachineAnnotationPostProcessorConfiguration class does not actually require any PostProcessor processing, SpringBoot is not intelligent enough to discern this. Though this warning is rather harmless, it can be somewhat bothersome to individuals with OCD😄.
The text was updated successfully, but these errors were encountered:
Have the following warning log when starting:
A possible solution:
Original code:
New code:
SpringBoot considers
StateMachineAnnotationPostProcessor
as aPostProcessor
. The creation of this bean necessitates the prior instantiation of theStateMachineAnnotationPostProcessorConfiguration
class. However, the instantiation of this class further requires allPostProcessor
s to process it, includingStateMachineAnnotationPostProcessor
. Consequently, this results in a warning log indicating that somePostProcessor
s cannot process it. While it's true that theStateMachineAnnotationPostProcessorConfiguration
class does not actually require anyPostProcessor
processing, SpringBoot is not intelligent enough to discern this. Though this warning is rather harmless, it can be somewhat bothersome to individuals with OCD😄.The text was updated successfully, but these errors were encountered: