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.
Now, with EJB 3.1, we can find the javax.ejb.Singleton annocation that can ensure that this bean is going to be singleton.
Is there a way that i can ensure singleton using stateless beans in EJB 3.0 with some modifications in my code (use of the keyword static, or other way to do that….)
If you’re able to limit your
@Statelessbean pool size to exactly 1, then you can get pretty close to an@Singleton.The effect would be like having an @Singleton that uses
@Lock(WRITE)for all calls (i.e. no concurrency) and does not eagerly startup via@Startup(it will start on first access).You might still be able to get the effect of
@Startupif your platform has the option to eagerly fill@Statelessbean pools.