Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <3EED1A48.4060306@joedog.org>
Date: Sun, 15 Jun 2003 21:15:52 -0400
From: Tim Funk <funkman@joedog.org>
Organization: Human being
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: Singleton across multiple contexts
References: <3EEC8F01.5030201@terra.es> <3EECA103.10603@joedog.org>
 <3EECB6D7.8090107@terra.es>
In-Reply-To: <3EECB6D7.8090107@terra.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Place the jar (or class) in common/lib (or common/classes) and all will be 
"ok". That is  - until you need to make a change to your singleton class (or 
a class used by it) - in which case you will need to restart tomcat. (and not 
restart your webapp)

-Tim

Antonio Fiol Bonn�n wrote:
> This is the best I could find:
> --------------
> Each application is loaded with sepperate classloaders, so as long as the
> servlets are in the same application and the singleton is in it's classpath
> too it works.
> --------------
> 
> My singleton has to work *across* applications.
> 
> Any ideas?
> 
> 
> Thank you very much.
> 
> 
> Antonio Fiol
> 
> 
> 
> Tim Funk wrote:
> 
>> Look in the archives and search for past Singleton discussions.
>>
>> http://marc.theaimsgroup.com/?l=tomcat-user&w=2&r=1&s=singleton&q=b
>> http://marc.theaimsgroup.com/?l=tomcat-dev&w=2&r=1&s=singleton&q=b
>>
>> Otherwise ...
>> - EJB (???)
>> - Use a custom JNDI Factory (see tomcat jndi docs)
>>
>> -Tim
>>
>> Antonio Fiol Bonn�n wrote:
>>
>>> Hello,
>>>
>>> This question is probably not specific to Tomcat, but a 
>>> Tomcat-specific answer could well suit my needs.
>>>
>>> I have an application which I have split in several different 
>>> contexts. I have done so, to allow different kinds of access to the 
>>> app, depending on the web server the requests are coming from.
>>>
>>> However, I need a common unique component that "ties" all the 
>>> contexts together.
>>>
>>> There must be a *single* instance of this component, otherwise 
>>> inconsistencies or duplicate work might arise. OTOH, it must be 
>>> accessible from all the contexts.
>>>
>>> Calls to this component are very simple (calls to void methods) but 
>>> moderately frequent.
>>>
>>> I have thought of several possibilities:
>>>
>>> - Extract the component into a separate JVM, and connect to it via 
>>> socket.
>>> - Extract the component into another context, and connect to it via 
>>> HTTP.
>>> --- I like none of those.
>>>
>>> - Create the instance from the first context needing it, and making 
>>> it available to all of them.
>>> --- I like this best, but I have no idea of how to do that.
>>>
>>>
>>> Yours sincerely,
>>>
>>>
>>> Antonio Fiol
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>
>>
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org