I use Tomcat 100% of the time, so, no, I don't have code to initialize the data-source. Sorry :-(
A ContextListener would also be another approach I forgot to mention. That's a servlet spec 2.3 thing - and would be even further independent of the particular app. Once written, you could drop into any app to init your data-source. If you find the need to externalize your configuration, see commons-digester -- it's a snap! (read the package docs for info on how to use digester - it is well documented through the javadocs) [EMAIL PROTECTED] wrote: >Thanks for this hint. >I am using tomcat 99% of the time, so it shouldn't be to bad. However I >like the traditional start-up servlet method better. Happen to have any >code on this (e.g. a start-up servlet...)? I know old school pooling >used start-up servlets too, and then you had to leave the pool in the >context. But with JNDI this should be easier. > >Stef. > -- Eddie Bush -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
