This is already given as a property torque.database.bookstore.adapter=mysql
for example. Patches so that torque does not require the connection pool if it not used are welcome. The run-test target is able to work without any pool configured, so I think it should already be possible, but maybe I am overlooking something? john mcnally On Fri, 2002-05-24 at 11:36, Subhash wrote: > Hello, > Given that the torque code has been changed to > accept datasources from JNDI, I would like to find out > if that is MANDATORY, as it is in the current design?. > > I can run the entire torque code by passing in a > Connection Object to all operations, and the only part > of the code that will fail is the Torque.getDB() call > since this needs to maintain a mapping between the > database name the DBAdaptor. Is that some thing that > we can pick up from a configuration file instead of > maintaining the mapping @ init time?. > > Would it be more appropriate to do some thing > like that?. If this is some thing that has enough > interest, then I am volunteering to make the change to > the torque code, and then submit the path. > > Thanks, -Subhash. > > __________________________________________________ > Do You Yahoo!? > LAUNCH - Your Yahoo! Music Experience > http://launch.yahoo.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
