The webapp has a login filter that needs a connection from the connection pool. The webapp loads the login filter first. I don't really want to remove the filter because its integral to the application's design. Is there another solution, to getting the connection pool instantiated before the filter?
Is this really a problem? Even though the filter needs a DB connection to do it's work, it doesn't need that connection until it's time to actually /do/ work, right?
You're certainly not going to get a request processed before the servlets are loaded, so it's probably alright that the DBCP is initialized *after* the filter itself.
Oh, and Yoav is right: you really want a ServletContextListener, rather than an 'init' servlet.
-chris
signature.asc
Description: OpenPGP digital signature
