Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 11
    the best singleton is the nonexistent singleton :) Commented Apr 28, 2011 at 17:49
  • Agreed with Bozho, especially in this case with ResourceBundle objects. ResourceBundle already caches previously retrieved bundles, so calling getBundle("bundle.name") is going to retrieve the existing one. Then just use that object as usual Commented Apr 28, 2011 at 18:16
  • ResourceBundles are already cache for your convenience, perhaps you can avoid all the singleton issue and trust the cache mechanism already in implemented in them. Commented Apr 28, 2011 at 19:18
  • 1
    You should cut down the detailed explanation in your question. Your question is more answer than question right now. It suffices to say where the recommendation came from and, briefly, why it is recommended. Commented Apr 29, 2011 at 11:31