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] Resolved: (JCR-1980) Create a database utility package
Date Wed, 02 Dec 2009 18:57:20 GMT

     [ https://issues.apache.org/jira/browse/JCR-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Martijn Hendriks resolved JCR-1980.

    Resolution: Duplicate
      Assignee:     (was: Martijn Hendriks)

The recent commits for JCR-1456 add the requested package (o.a.j.core.util.db) so I resolved
this issue as "duplicate" (that doesn't really describe it but it's the closest option I think).

> Create a database utility package
> ---------------------------------
>                 Key: JCR-1980
>                 URL: https://issues.apache.org/jira/browse/JCR-1980
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>         Environment: All
>            Reporter: Martijn Hendriks
> Currently, many classes implement their own database utility methods. For instance, the
classes o.a.j.core.fs.db.DatabaseFileSystem, o.a.j.core.data.db.DbDataStore, o.a.j.core.persistence.bundle.BundleDbPersistenceManager,
o.a.j.core.persistence.db.DatabasePersistenceManager and o.a.j.core.journal.DatabaseJournal
all contain methods to initialize the DB schema, to reconnect if a connection is lost, to
get a new connection, etc. This gives rise to duplication and maintenance problems: see, e.g.,
JCR-1362, JCR-814 and JCR-582.
> It would be nice to have a single package with (database specific) classes that implement
all needed database functionality. Having all this code in a central place makes maintenance
a lot easier. Furthermore, it might help us to implement much wanted features like connection
pooling (JCR-1456).

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

View raw message