You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2007/08/29 15:33:30 UTC
[jira] Updated: (JCR-1097) Move the XASession interface to
jackrabbit-api
[ https://issues.apache.org/jira/browse/JCR-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1097:
-------------------------------
Attachment: XASession.patch
Attached a proposed patch (XASession.patch). I'm not sure about all the implications of this move, so please review.
The previous o.a.j.core.XASession interface would remain as a deprecated interface that simply extends o.a.j.api.XASession. The existing XASessionImpl would also for now keep implementing the deprectated o.a.j.core.XASession interface instead of the new jackrabbit-api version to avoid backwards compatibility issues.
> Move the XASession interface to jackrabbit-api
> ----------------------------------------------
>
> Key: JCR-1097
> URL: https://issues.apache.org/jira/browse/JCR-1097
> Project: Jackrabbit
> Issue Type: Improvement
> Components: transactions
> Reporter: Jukka Zitting
> Priority: Minor
> Attachments: XASession.patch
>
>
> As discussed in JCR-953, it would probably make sense to move the org.apache.jackrabbit.core.XASession from jackrabbit-core to jackrabbit-api as org.apache.jackrabbit.api.XASession.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.