Hi Pat,
Thank you for your reply.
What, precisely, is the nail that you are trying to hammer with the singleton pattern?
I understand that singletons should be avoided and the usage is often the result of bad design.
I want to report statistics and information based on class usage in different parts of my code.
There are issues before you get to the complexity of clustered environments.
Are there some standard java libraries or popular third party libraries that should be avoided in Java EE Servers for this reason?
I am interested to know what the major issues you are referring too are.
If we ignore the "bad design" aspect of singleton's what will be the difference to a java ee server if you use a singleton bean vs a singleton object to hold distinct information about classes as per example below.
Thank you
Eric