Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Reply-To: <jacob.blain.christen@entheal.com>
From: "Jacob L E Blain Christen" <jacob.blain.christen@entheal.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Subject: RE: Singleton across multiple contexts
Date: Wed, 18 Jun 2003 17:10:07 -0400
Message-ID: <NCENIGFDOFMJCOJGBLCJAEBMCAAA.jacob.blain.christen@entheal.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <3EECB22D.70907@terra.es>

> I do have a database. Databases are supposed to store data, 
> aren't they? ;-)

Yeah, which is why ...

> Now seriously... My application includes a web interface to a "kind of" 
> workflow system.
> 
> This component is the "workflow engine", which is in charge for 
> automatic (background) state changes and actions. When my 
> business/persistence logic changes a state, new potential tasks for this 
> "engine" arise. So it has to be notified (=called) from any context that 
> may change a state.

... you should use one here.  You are describing state changes that need
to happen in an atomic manner and "exist" in one and only one place.
The semantics of db interactions are perfectly suited for what you are
trying to do.

--
Jacob L E Blain Christen
Entheal LLC

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