[
https://jira.jboss.org/jira/browse/DNA-392?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-392:
-----------------------------------
Changed the JcrRepository implementation to have a new option that defines the source name
(and optionally workspace name) where the /jcr:system branch is to be found. If this
option is not used, or if the supplied names do not correspond to a valid workspace in an
existing source, a transient in-memory source will be used. The existing JcrConfiguration
and JcrEngine are already able to process any options, so they do not need to be changed
to allow a configuration to define the /jcr:system branch location.
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