You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2008/01/25 14:40:34 UTC
[jira] Updated: (JCR-1349) JNDIDatabasePersistenceManager calls
commit
[ https://issues.apache.org/jira/browse/JCR-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller updated JCR-1349:
--------------------------------
Issue Type: New Feature (was: Bug)
Jackrabbit does not support this mode of operation right now.
To support it, we would need to define exactly how this mode should behave,
for example: should the Session.save() calls be silently ignored, or should they
throw an exception (like commit() throws an exception).
> JNDIDatabasePersistenceManager calls commit
> -------------------------------------------
>
> Key: JCR-1349
> URL: https://issues.apache.org/jira/browse/JCR-1349
> Project: Jackrabbit
> Issue Type: New Feature
> Components: jackrabbit-core
> Affects Versions: 1.4
> Reporter: Jarle B. Hjortland
>
> It is not possible to configure either JNDIDatabasePersistenceManager or BundleDbPersistenceManager to use a Managed Datasource. Methods like setAutoCommit, commit and rollback should not be called on managed connections.
> Try to run Jackrabbit within JBOSS or Apache Geronimo and you should face the same problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.