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] Updated: (JCR-1671) Support for external datasources with transactions
Date Mon, 21 Jul 2008 13:33:32 GMT

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

Jukka Zitting updated JCR-1671:

          Component/s: jackrabbit-core
             Priority: Major  (was: Critical)
    Affects Version/s:     (was: 1.3.1)
        Fix Version/s:     (was: 1.3.1)
           Issue Type: Improvement  (was: Wish)
              Summary: Support for external datasources with transactions  (was: Support for
external datasources with transactions in 1.3.1)

I'm not sure what you mean with "external datasources" here. Do you mean an external database?

Jackrabbit (including all 1.3.x versions) already supports transactions with all database
persistence managers. Note however that the underlying database needs to be under direct control
of Jackrabbit, i.e. you must not use an external transaction manager on the data source that
Jackrabbit uses.

> Support for external datasources with transactions
> --------------------------------------------------
>                 Key: JCR-1671
>                 URL: https://issues.apache.org/jira/browse/JCR-1671
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core, transactions
>         Environment: Websphere application server 6.0, DB2 database
>            Reporter: Badal
> Jackrabbit 1.3.1 should support transactions with external datasources

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

View raw message