RE: RE: Event Processing at servlet startup..

> you can always write up a separate configuration servlet that 
> gets loaded on startup just like ApplicationGateway, only make 
> it load before ApplicationGateway by giving it a lower number 
> than the applicaton gateway servlet's value.  For instance, if 
> the application gateway currently has 
> <load-on-startup>1</load-on-startup> then change that to 2 
> and give your setup servlet the "1" value.  That will be enough to 
> guarantee that by the time requests are taken by the application 
> gateway, all initialization will have been done and then you can 
> remove special login request event listener.

Hey, sounds just like the ObjectRepositoryAssembler ;-)

Christian
----------------------------------------------
Christian Cryder
Internet Architect, ATMReports.com
Project Chair, BarracudaMVC - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today" 


> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Jacob Kjome
> Sent: Tuesday, June 17, 2003 12:43 PM
> To: [email protected]
> Subject: RE: [Barracuda] RE: Event Processing at servlet startup..
> 
> 
> At 04:40 PM 6/17/2003 +0200, you wrote:
> 
> I'll look into creating using 'contextInitialized'.
> At the moment.. we'll be using Tomcat 3.3 in production.
> I hope it has this facility. 
> 
> Hmm.... That's tough.  Tomcat-3.3.x is still servlet 2.2 and, as 
> such, you will not be able to utilize the Barracuda 1.2.0 
> multiple assembler file loading, although you can still use your 
> own file-based version.
> 
> You also won't be able to use a servlet context listener since 
> that is also servlet 2.3.  However, you can always write up a 
> separate configuration servlet that gets loaded on startup just 
> like ApplicationGateway, only make it load before 
> ApplicationGateway by giving it a lower number than the 
> applicaton gateway servlet's value.  For instance, if the 
> application gateway currently has 
> <load-on-startup>1</load-on-startup> then change that to 2 and 
> give your setup servlet the "1" value.  That will be enough to 
> guarantee that by the time requests are taken by the application 
> gateway, all initialization will have been done and then you can 
> remove special login request event listener.
> 
> Does that solve your issues?
> 
> Jake