Just a thought, but why not use the DataSource and Connection interfaces internally and implement those with the ConnectionPool and DBConnection? DataSource and Connection are already interfaces designed (and widely used) to support connection pooling. Jeff Schnitzer [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -----Original Message----- From: Bill Schneider Sent: Tue 4/16/2002 6:05 AM To: Turbine Torque Users List; [EMAIL PROTECTED] Cc: Subject: Re: Torque and data sources I've wanted to do the same thing and haven't gotten around to implementing this yet. It should be fairly straightforward to break the ConnectionPool and DBConnection classes in org.apache.torque.pool into an interface + implementation, then make a second implementation that pulls from JNDI. There's also a CVS branch that binds a Torque connection pool *to* JNDI but I'm not sure how well this works. In practice, if you're using JNDI to look up a data source, you're almost always doing it because you have a datasource already available that you just have to reference. -- Bill ----- Original Message ----- From: "Ken Rimple" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 16, 2002 12:27 AM Subject: Torque and data sources > This is my first posting to the group. Apologies if I say anything stupid > here. > > First off, I am VERY impressed with torque. I have a question, however > about how you would use Torque in an application server environment not > powered by turbine, etc., ie-- a J2EE appserver requiring a datasource. > > Is there a set of configuration parameters that would let the runtime > pull a connection out of a jndi datasource? For example, my world is > BEA Weblogic, and all container-managed transaction processing is performed > by the container, but only if you use a jndi datasource to pull in the > connection. > > Thanks for any pointers, or if anyone else out there is using torque > against weblogic or jboss, etc. > > Ken Rimple > [EMAIL PROTECTED] > > > -- > 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]>
<<winmail.dat>>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
