jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1456) Database connection pooling
Date Sat, 30 May 2009 07:58:07 GMT

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

Jukka Zitting commented on JCR-1456:
------------------------------------

My concerns about too many changes were mostly about having the modifications go too much
beyond the o.a.j.core.persistence package (and other database-related packages). What we do
inside those packages is open for discussion, and I'd personally prefer to reach a clean design
that's built with connection pooling in mind than to patch the current design to work with
pooled connections.

Anyway, I think the Context class is a good starting point, and we can continue by refactoring
until the design is better.

Fair point about the one big change. If you like you can commit the full patch as-is and we
can work from there in svn.

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


Mime
View raw message