jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martijn Hendriks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1456) Database connection pooling
Date Thu, 30 Jul 2009 13:31:15 GMT

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

Martijn Hendriks commented on JCR-1456:

In order to make testing on other databases than Derby easier, I've created a new profile
in jackrabbit-core and new configuration files in src/test/repository-filtered.
The profile copies the test configuration files from src/test/repository-filtered and filters
them against properties specified in the pom. The core tests can then be run, e.g., against
a configuration which puts all data in a MySQL database.

I think that this makes testing the core against other than the Derby backend easier. Shall
I commit this to the sandbox branch which has been created for this issue?

> 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,
> 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.

View raw message