By default, the Bean created by Spring is singleton. They are thread-safe because they are stateless. When we want Spring to create a stateful Bean, we need to use prototype scope for the Bean definition. We need to take care of the thread-safe issues for them. All stateless Bean will be polluted when they are injected by the prototype bean. So, I just can not image where we can use the prototype scope. Can you give some typical scenario that we can / need to use prototype Spring Bean? Also how can we void the stateful pollution on other singleton beans?
By default, the Bean created by Spring is singleton. They are thread-safe because they
Share
There are many reasons to use prototype scope, e.g., any time you’d use “new” instead of using a singleton. A per-user bean, a per-request bean, a collection of unique beans, etc. After all, in any non-trivial application, don’t you use non-singletons far more than singletons?
Singleton-scoped beans aren’t thread-safe simply because they’re singletons–they must be written to be thread-safe. They don’t become thread-safe magically. A bean’s scope is just that, its scope: it doesn’t make the bean appropriate for the particular scope–that’s up to the developer.