Add cycles to core-beans: the circular-dependency failure report, what allow-circular-references repairs and hides, and four fixes on Boot 4.1
Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Uu7q8vPeREyT4218EJPzz1
This commit is contained in:
@@ -0,0 +1,12 @@
|
||||
# Fix 4: ObjectProvider<OrderService> in NotificationService
|
||||
|
||||
started: true
|
||||
place("kettle") -> order placed: charged, e-mail says: 1 x kettle
|
||||
|
||||
--- the same provider, but getObject() is called inside the constructor ---
|
||||
started: false
|
||||
root cause: Error creating bean with name 'cycleFixesTest.EagerNotifier': Requested bean is currently in creation: Is there an unresolvable circular reference or an asynchronous initialization dependency?
|
||||
|
||||
--- the provider needs no proxy, so a final class is fine ---
|
||||
started: true
|
||||
hello() -> hello
|
||||
Reference in New Issue
Block a user