[jira] Created: (JCR-1671) Support for external datasources with transactions in 1.3.1

View: New views
6 Messages — Rating Filter:   Alert me  

[jira] Created: (JCR-1671) Support for external datasources with transactions in 1.3.1

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Support for external datasources with transactions in 1.3.1
-----------------------------------------------------------

                 Key: JCR-1671
                 URL: https://issues.apache.org/jira/browse/JCR-1671
             Project: Jackrabbit
          Issue Type: Wish
          Components: transactions
    Affects Versions: 1.3.1
         Environment: Websphere application server 6.0, DB2 database
            Reporter: Badal
            Priority: Critical
             Fix For: 1.3.1


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.


[jira] Updated: (JCR-1671) Support for external datasources with transactions

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


     [ 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.


[jira] Commented: (JCR-1671) Support for external datasources with transactions

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ https://issues.apache.org/jira/browse/JCR-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615539#action_12615539 ]

Badal commented on JCR-1671:
----------------------------

I want to JackRabbit to work with external transaction manager. Jackrabbit should retrieve the connection through JNDI which is part of JTA transaction.
Any transaction done by JackRabbit will be part of global transaction and its commit/rollback will be decided by global transaction.

If this is not supported in 1.3, is this supported in any of the future releases?

> 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.


[jira] Resolved: (JCR-1671) Support for external datasources with transactions

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


     [ 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.


[jira] Commented: (JCR-1671) Support for external datasources with transactions

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ https://issues.apache.org/jira/browse/JCR-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615650#action_12615650 ]

Badal commented on JCR-1671:
----------------------------

Is there any documentation around managed transaction and any reference implementation details?

> 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.


[jira] Commented: (JCR-1671) Support for external datasources with transactions

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ https://issues.apache.org/jira/browse/JCR-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616001#action_12616001 ]

Jukka Zitting commented on JCR-1671:
------------------------------------

> Is there any documentation around managed transaction and any reference implementation details?

Not much. There are some related threads on the Jackrabbit mailing lists, you can find them by searching at http://jackrabbit.markmail.org/.

> 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.