[ https://issues.apache.org/jira/browse/JCR-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881557#action_12881557 ]
Claus Köll commented on JCR-890: -------------------------------- Hi Jukka, I saw your commits with the new SessionOperations. First good work but i want to let you know that the locking is only Thread based and we will get some problems in a xa environment on a applicationserver because the reentrant calls must not come from the same thread. I would prefere to handle now the whole locking semantic in our own classes to handle this behaviours in a global way. See JCR-2089 > concurrent read-only access to a session > ---------------------------------------- > > Key: JCR-890 > URL: https://issues.apache.org/jira/browse/JCR-890 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-core > Reporter: David Nuescheler > Assignee: Jukka Zitting > Fix For: 2.2.0 > > Attachments: session-class-move-norename.patch, > session-class-move.patch > > > Even though the JCR specification does not make a statement about Sessions > shared across a number of threads I think it would be great for many > applications if we could state that sharing a read-only session is supported > by Jackrabbit. > On many occasions in the mailing lists we stated that there should not be an > issue with sharing a read-only session, however I think it has never been > thoroughly tested or even specified as a "design goal". > If we can come to an agreement that this is desirable I think it would be > great to start including testcases to validate that behaviour and update the > documentation respectively. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.