spring initialization order
suppose i have integrate open beans:
<beans>
<bean name="a" ... />
<bean name="b" ... />
</beans>
"b" exposes remote use doesn't need "a". assume "a" takes non-negligble load. means during restart cycle, concentration hangs remote client, indeed bond server nonetheless waits response until open enclosing entirely initializes.
what i'd means have "b" remote use respond immediately, even (based concentration state) wholly relapse not_ready such. container, however, army wait until it's beans initialized, even mention beans lazy-init irrespective bucket order.
i think carrying "b" accessible immediately meant open have accessible partially initialized container, sounds bad. however, i'd conclude any information anyone's got initialization method presumably you've found any reasonable workarounds.
Comments
Post a Comment