This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
Using classical singleton pattern in J2EE environment is not a good idea. It's a pain in the ass when the "singleton" might not be singleton as you might expected. One such situation might be when there exists a hierarchy of classloaders in different J2EE modules where each might load their own "singleton". You might face problem also when in distributable web application.
If you need to ensure real "singleton" object in your environment, an entity bean would do the trick.
SCJP, SCWCD, SCJWS, IBM 700,IBM 701, IBM 704, IBM 705, CA Clarity Technical<br /> <br /><a href="http://eddyleesinti.blogspot.com" target="_blank" rel="nofollow">http://eddyleesinti.blogspot.com</a>