[jira] [Commented] (JCR-3206) JSR-283 support for RMI

["Claus Köll (JIRA)" <ji...@apache.org>]

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

Claus Köll commented on JCR-3206:
---------------------------------

Hi Lars,

>The current implementation always returns a new RemoteStub for every access to a remote method. 
>This means, one can execute getSession() on a node and always create a new ServerSession as adapter which gets registered in the RMI registry. 
I can't really follow you here. On a ClientNode getSession() returns always the ClientSession without any server roundtrip.

On which objects/level should your cache work ? Lets assume following test ...
Node x = session.getNodeByUUID();
Node y = session.getNodeByUUID();
Your cache will not work because on the server side the 2 "same" Nodes have different hashCode's
The remoteCache uses a ReferenceIdentityMap which calculates the hashCode of jcr objects with System.identityHashCode.
This will not work for many jcr objects.

In the current impl some objects will be already cached with member variables like workspace in ClientSession or
lockManger in ClientWorkSpace.

I think we should define what objects we use with your cache.
                
> JSR-283 support for RMI
> -----------------------
>
>                 Key: JCR-3206
>                 URL: https://issues.apache.org/jira/browse/JCR-3206
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-jcr-rmi
>    Affects Versions: 2.3
>            Reporter: Claus Köll
>         Attachments: jackrabbit.diff, jackrabbit-jcr-rmi-ntm-ac-ej.patch, rmi-cache-updated.patch, rmi-eventjournal.patch
>
>
> We have the JCRRMI-26 Issue for the missing JSR-283 support.
> As we do no more use the Jira Project JCRRMI i would like to create a new Issue for that feature request.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira