Hmm, I thought struts-config.xml solved this problem. You can configure your datasources there and access them from the ServletContext. You could add a reference to them in JNDI on application start up as well.
If you're not using struts then you'll need to use a container and/or application specific approach. Dave >From: "Bradley G Smith" <[EMAIL PROTECTED]> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >Subject: Datasource Access Options (was Connection Pooling) >Date: Tue, 15 Oct 2002 09:15:51 -0700 > > >I spent much of yesterday using Google to glean information about >configuring Struts (w/ Tomcat in my case) to use a datasource. As Eddie >Bush points out in a prior post options for initializing a datasource (with >or without a connection pool) include: > >1. Tomcat JNDI service via server.xml; >2. An initialization servlet; >3. A Struts plugin (1.1 or newer I believe) >4. Singleton pattern. > >And I suppose a fifth option might be using a persistence framework which >would possibly implement one of the above behind the scenes more or less. >Some useful info on persistence frameworks is at: > >http://www.rollerweblogger.org/page/roller/20021013 > >Does anyone have any thoughts of selection criteria that would inform a >choice between them? In my case, I would be using Oracle drivers which do >have a connection pool built-in (JDBC 2). > >Thanks, > >Brad > > > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> _________________________________________________________________ Join the world’s largest e-mail service with MSN Hotmail. http://www.hotmail.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
