The typical form is like this
public class SingletonObject
{
private SingletonObject(){}
public static SingletonObject getSingletonObject()
{
if (ref == null)
// it's ok, we can call this constructor
ref = new SingletonObject();
return ref;
}
private static SingletonObject ref;
}
If thats in Tomcat/lib.... it should share
Notice the use of static.... ie there is only one, no matter how many times
its started.
...and the check for null.... which is how it determines it needs to make
one instance if there is non...
Thats the trick.... a normal class which is what I imagine you trying, will
load once..... but instance many times.
Hope that helps... try not use them unless you really have to.
----- Original Message -----
From: "Kevin Wilhelm" <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Monday, June 18, 2007 3:12 PM
Subject: Share one singleton across webapps
I managed to get a jar file shared across two webapps in my Tomcat 6.
Inside there is a class that represents a Singleton.
The problem: the singleton class is instantiated by the first webapp and
then again instantiated in the second webapp. So there are 2
representations of the class and it is not really shared.
There has to be a way to let the first webapp instantiate the singleton
and set some property so that the second webapp can use the singleton
and read the property. How do I achieve this?
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
