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] Resolved: (JCR-2578) Deprecate XASession
Date Tue, 13 Apr 2010 11:18:49 GMT

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

Jukka Zitting resolved JCR-2578.
--------------------------------

         Assignee: Jukka Zitting
    Fix Version/s: 2.2.0
       Resolution: Fixed

Patch committed in revision 933554.

> Deprecate XASession
> -------------------
>
>                 Key: JCR-2578
>                 URL: https://issues.apache.org/jira/browse/JCR-2578
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-api, jackrabbit-core, jackrabbit-jca, transactions
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 2.2.0
>
>         Attachments: JCR-2578.patch
>
>
> The XASession interface in jackrabbit-api extends Session with a single getXAResource()
method. The idea is that a transactional client (or a transaction manager) will test whether
a session implements XASession and can then get the XAResource instance that can be used to
bind the session to a distributed transaction. The essential code is:
>     if (session instanceof XASession) {
>         return ((XASession) session).getXAResource();
>     }
> This works fine except for the extra dependency to jackrabbit-api that it introduces
in code that otherwise would only need the JCR API. Since the link between a transaction-enabled
session and the related XAResource instance is always one-to-one, we could avoid this dependency
by making the session directly implement XAResource, leading to code like this:
>     if (session instanceof XAResource) {
>         return (XAResource) session;
>     }
> This is essentially what jackrabbit-jcr-rmi did in 2.0.0 to avoid the jackrabbit-api
dependency while maintaining XA transaction support, and I'd like to extend this solution
also to other parts of Jackrabbit.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message