On Mon, 2 May 2005 16:32:07 +0100, Gregory Block wrote:
>
>On 1 May 2005, at 08:20, Werner Guttmann wrote:
>
>> Mike,
>>
>> have a look at
>>
>> http://castor.codehaus.org/pooling.html#Jakarta-Commons-DBCP---
>> BasicDataSource
>>
>> which has details about how to use and configure DBCP with Castor
>> and Tomcat. Wrt 'prepared statement cache', Gregory
>> seems to be referring to the fact that DBCP is JDBC 3.0-compliant
>> product as as such has to support caching of prepared
>> statements. This basically allows the JDBC driver to maintain a
>> pool of prepared statements across all connections.
>>
>
>Correct.
>
>DBCP setup is generally outside of the scope of this list, but
>basically, here's my two cent description:
>
>1) Use tomcat 5.5, because mucking about in server.xml sucks.
For those of you working with Tomcat 4.1.x, there's no need to muck about in
server.xml, either. Afaik, a web app can be
deployed using a web app descriptor copied into $TOMCAT_HOME/webapps, which is
the place top define anything specific
to a web app context, as outlined by Greg below. Details can, of course,
>2) Create a META-INF directory in your WAR deploy scripts, and put a
>context.xml in it.
>3) In that context.xml, describe all of the things you want to be
>made available via JNDI to your application. These include things
>like UserTransaction and TransactionManager (for those of us using
>JOTM), all your database connection pools as datasources, etc. You
>can also add your JDO factory here, should you choose to do so.
>4) Configure Castor to load those JNDI names to retrieve connections.
>
>Hit the deploy button, and bob's your uncle.
>
