How does Spring resolve this: bean A is dependent on bean B, and bean B on bean A.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How does Spring resolve this: bean A is dependent on bean B, and bean B on bean A.
As the other answers have said, Spring just takes care of it, creating the beans and injecting them as required.
One of the consequences is that bean injection / property setting might occur in a different order to what your XML wiring files would seem to imply. So you need to be careful that your property setters don’t do initialization that relies on other setters already having been called. The way to deal with this is to declare beans as implementing the
InitializingBeaninterface. This requires you to implement theafterPropertiesSet()method, and this is where you do the critical initialization. (I would also include code to check that important properties have actually been set.)