Can't help it.... number two :) ....now this is getting silly! I myself usually choose to set up the connections in the source code, so I can move my entire DAO layer anywhere (swing frontend for instance) with no changes at all. Really though, I don't think it would take much effort to change my connection code (which is used the Jakarta pooling stuff) to access a container managed connection.
Scott Barr www.exergonic.com.au On Tue, 2003-03-25 at 14:35, Kwok Peng Tuck wrote: > I usually pick number two (if you are refering to a jndi datasource) > and leave the configuration to tomcat. So it's possible for me to move > the apps to another app server > without changing my sql code. Just have to configure the same datasource > over in the new app > server. > > > Mark Galbreath wrote: > > >I've read the literature and nothing seems definitive. Apparently we can > >declare a data source by: > > > >1. Declaring it in struts-config; > > > >2. Declaring it in the container app; > > > >3. Declaring it in the source code; > > > >4. Declaring it in the deployment descriptor; > > > >5. Declaring it in the EJB deployment descriptor. > > > >Is it just me or is this a pile of this? > > > >Mark > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
