You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Berry van Halderen (JIRA)" <ji...@apache.org> on 2007/05/30 14:06:19 UTC

[jira] Commented: (JCR-953) Support for transactions when using JCR over RMI.

    [ https://issues.apache.org/jira/browse/JCR-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500111 ] 

Berry van Halderen commented on JCR-953:
----------------------------------------

I think the only thing that needed to be implemented is to extend both client and server side decorator stubs to implement the XAResource interface.  The client, when asked for the getXAResource() can just return itself.  In the implementation of the XAResource interface the client stub can just call the server side stub over RMI.  The server side stub just
forwards the call to the actual session.  This works because the transaction IDs (Xid) are serializable, and can be passed over RMI.  The transactions themselves are managed at the client side.
I will be providing a proposal patch for this shortly.


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