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.
just reading up on spring, and when using DI in spring, if you set the bean to be a singleton (default), then a single instance of the class will be ‘dispensed’, while prototype forces a new instance each time.
What are the ramifications of having the same instance dispensed by the container each time?
does that mean there will be shared state?
i.e. if the instance is modified somewhere, all future object creations will actually be getting a ‘dirty’ object and not a ‘new’ one?
Since you’re usually programming to an interface with Spring, the objects that are DI managed don’t have state to worry about. There’s no concern about “dirty” in that case. Repositories, services, controllers – all should have little or no state to speak of.