[
https://issues.apache.org/jira/browse/JCR-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-744.
-------------------------------
Resolution: Won't Fix
Assignee: Jukka Zitting
The database persistence manager assumes full control of the database
connection, so you can't have it under the control of an external transaction.
Instead of the underlying database connection you should have the JCR Session
included in a potential distributed transaction.
Resolving this as Won't Fix as the described behaviour is a feature of the
current design.
> DatabasePersistenceManager
> --------------------------
>
> Key: JCR-744
> URL: https://issues.apache.org/jira/browse/JCR-744
> Project: Jackrabbit
> Issue Type: Bug
> Components: core
> Affects Versions: 1.2.1
> Environment: Jackrabbit as J2C Adapter in EJB Container
> Reporter: Claus Köll
> Assigned To: Jukka Zitting
>
> If you are using a JNDIDatabasePersistenceManager and pointing to a
> XADataSource
> its not allowed to call connection.commit.
> In a global Transaction a explicit commit call is permited.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
