[dna-issues] [JBoss JIRA] Commented: (DNA-392) All sessions in a repository should share the same /jcr:system content

[Randall Hauch (JIRA)]

    [ https://jira.jboss.org/jira/browse/DNA-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12477080#action_12477080 ] 

Randall Hauch commented on DNA-392:
-----------------------------------

Changed how the JcrSession and JcrWorkspace objects are instantiated to move all content initialization code into the JcrRepository class.  Creating JcrSession and JcrWorkspace objects is not much faster, though there still is a single verify workspace request issued against the source (even though this is still done within the JcrRepository instance, the JcrWorkspace creates its own graph, which requires issuing this request).  Changed a number of test cases to reflect the new behavior.

> All sessions in a repository should share the same /jcr:system content
> ----------------------------------------------------------------------
>
>                 Key: DNA-392
>                 URL: https://jira.jboss.org/jira/browse/DNA-392
>             Project: DNA
>          Issue Type: Task
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.6
>
>
> Currently each JcrSession has its own copy of the /jcr:system content branch.  Technically this is incorrect, since all of the information in this branch is common to and shared by all sessions/workspaces in the repository.  One approach to making this work is to have a special workspace in the repository in which the content from the "/jcr:system" branch is placed, and have this workspace projected into each session.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira