Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of ben@souther.us designates
 74.119.145.130 as permitted sender)
Subject: RE: Permanent servlet in TC7
From: Ben Souther <ben@souther.us>
To: users@tomcat.apache.org
Date: Fri, 27 Jul 2012 16:55:30 -0400
In-Reply-To: 
 <774CCD676B63FE49B1291BE556DD698522747B1A@ALVMBXW02.prod.quest.corp>
References: 
	<774CCD676B63FE49B1291BE556DD698522747AA7@ALVMBXW02.prod.quest.corp>
	 <50119C9F.9010601@christopherschultz.net>
	 <774CCD676B63FE49B1291BE556DD698522747B1A@ALVMBXW02.prod.quest.corp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Message-ID: <1343422531.13485.32.camel@localhost.localdomain>
Mime-Version: 1.0

On Thu, 2012-07-26 at 19:54 +0000, Chip McVey wrote:
> So I'm looking for a guarantee that no automatic destroys will happen
> going forward just because Tomcat decides to do it on its own.  If it
> is instructed to shutdown/undeploy/unload by some outside system or by
> a human user, that's fine, I'm not worried about that.  But I don't
> want these servlets to be destroyed just because Tomcat decides to do
> so for whatever reason.

If I were looking for permanence, I would create POJO, bind it to
context scope, and then call it from my servlets, passing it whatever it
needs to function.


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