Analogue of stateless and statefull beans in Spring?

Either you can make the bean thread-safe, and a singleton bean is OK (that's the majority of the cases).

Either you can make the bean thread-safe, and a singleton bean is OK (that's the majority of the cases). Or you can't, and you'll have to use a prototype. The difference I see between Spring prototype beans and stateless EJB session beans is that stateless session beans are pooled.

But in these ages, pooling them or creating a new instance each time won't make much difference. Creating a new instance each time might even help the GC.

Pools also help with automatic resource throttling by setting the pool to an appropriate size. Furthermore, the bean instance might be cheap, but its associate resources might not be. Also, by using a proxy + pool pattern, injecting many 'beans' becomes very cheap and is no problem even if they end up not being used.

Since the proxy in case of stateless beans is just akin to a URL that point to the pool. – Arjan Tijms Oct 30 at 17:27.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.