[
https://issues.apache.org/jira/browse/JCR-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523554
]
Berry van Halderen commented on JCR-953:
----------------------------------------
Indeed, the jackrabbit-core dependency is pretty ugly. There is no proper way
other than to pull the XASession out of the core into the api. This would be a
simple move operation and would cleanly fix it. It is a pitty that the
XASession interface did not make it into the specification. I saw that in
earlier draft there was a reference to this:
http://www.day.com/maven/jsr170/javadocs/jcr-0.15/javax/jcr/xa/XASession.html
But it did not make it into the spec. It strikes me as an omission that the
spec defines a level for transaction, but not an interface to obtain a
XAResource (as is given by XASession).
> Support for transactions when using JCR over RMI.
> -------------------------------------------------
>
> Key: JCR-953
> URL: https://issues.apache.org/jira/browse/JCR-953
> Project: Jackrabbit
> Issue Type: Improvement
> Components: rmi
> Reporter: Berry van Halderen
> Priority: Minor
> Attachments: patch, test.zip
>
>
> At this time, the sessions obtained from o.a.j.rmi.client.LocalAdapterFactory
> do not implement the methods for the XASession. Therefor the RMI access
> layer does not support a transactional session.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
