Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1145585771.1216714711825.JavaMail.jira@brutus>
Date: Tue, 22 Jul 2008 01:18:31 -0700 (PDT)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-1671) Support for external datasources with
 transactions
In-Reply-To: <615435786.1215450152517.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jukka Zitting resolved JCR-1671.
--------------------------------

    Resolution: Won't Fix
      Assignee: Jukka Zitting

You can make a Jackrabbit session a part of a managed transaction so there's no need (and it's in fact harmful) to manage the underlying database connection. See for example the jackrabbit-jca component where JCR sessions are automatically associated with a transaction manager.

Resolving this issue as Won't Fix.

> 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
>            Assignee: Jukka Zitting
>
> 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.