[
https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714472#action_12714472
]
Matej Knopp commented on JCR-1456:
----------------------------------
Thanks for the feedback.
Unfortunately most of the patch is one big change - it modifies
AbstractBundlePersistenceManager so it requires all it's subclasses to be
adapted.
The context class was IMHO probably the easiest way to introduce connection
pooling without requiring complete refactor/rewrite of persistence managers.
Yet the patch is quite big.
I like the idea of operations. This would however be far bigger change that
what I did. I thought the idea was to introduce connection pooling with minimal
fuzz. Looks like I was wrong. I will look into this. I agree that if done
properly this would be much cleaner solution than passing context object around.
> 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.
