[ 
https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738108#action_12738108
 ] 

Martijn Hendriks commented on JCR-1456:
---------------------------------------

Committed in revision 800118. Using a different DB backend for testing can be 
done as follows:
* Edit the relevant properties in the pom of the jackrabbit-core's 
use-descriptor-overlay profile.
* Make sure you have the appropriate DB driver on the classpath (a MySQL driver 
is already there)
* Run mvn clean integration-test -Puse-descriptor-overlay

Note that the profile drops and recreates the test database in the clean phase.

I recently have been looking at refactoring the database classes a bit to 
remove duplication in e.g., all these bean properties (username, password, 
schema object prefix, etc) and, more importantly, methods like checkSchema. The 
idea was to have a base class, say DbSupport, with all these common properties 
and methods and and with a method to get a sort of JDBC helper class which 
encapsulates the Connection and operations on it (something like the 
ConnectionRecoveryManager). I had various subclasses of the JDBC helper in mind 
for the various DB types (Oracle9, Derby). This works quite nicely for the 
core.fs.db package and connection pooling can then be located inside that JDBC 
helper class. I was wondering if that could help us here. What if the 
Operations that are mentioned above use such as JDBC helper class?

> Database connection pooling
> ---------------------------
>
>                 Key: JCR-1456
>                 URL: https://issues.apache.org/jira/browse/JCR-1456
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>         Attachments: 777490.patch, dbcp.patch, dbcp.patch, patch-1456-1.txt, 
> patch-1456-2.txt, patch-1456-3.txt
>
>
> Jackrabbit should use database connection pools instead of a single 
> connection per persistence manager, cluster journal, or database data store.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to