Title: How to handle processing that would have been in Servlet's init routine

Nothing prevents you from having an Initialize servlet that coexists with your Maverick application.  FWIW, most of my webapps have an Initialize servlet. 

 

Just create a servlet, give it a load-on-startup, and don’t map anything to it.  Implement whatever you want in the init() method.

 

3jeff

 

 

-----Original Message-----
From: Eder, Warren CONT [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 30, 2003 8:47 AM
To: [EMAIL PROTECTED]
Subject: [Mav-user] How to handle processing that would have been in Servlet's init routine

 

What are best pratices in Maverick for handling things that would of been done in a Servlet's init routine.  Specifically I would like to set up connection pooling for all future Oracle database connections.

Your suggestions are appreciated.

Warren Eder
504-697-3324

Reply via email to