[
https://issues.apache.org/jira/browse/SLING-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-1447:
----------------------------------
Summary: support for resource paths containing workspace name (was:
jcr resource events are only created for the default workspace)
Component/s: JCR
changing name to reflect increased scope.
As discussed on the mailing list (http://markmail.org/thread/2xpbrnvfqmcwggyi),
the initial implementation was flawed in that it added a new event property
containing the workspace. Instead, the resource path should contain the
workspace name as:
[workspace]:[path_within_workspace]
In order to do that, this type of resource path must be resolveable and
resources returned by the ResourceResolver interface methods must return the
correct path values.
Each JcrResourceResolver is associated with a single primary session. This is
either the default session or one specified using the user.jcr.workspace auth
info property. In the case where a ResourceResolver gets a request for a
resource path in a different workspace, it should ask the factory for a new
resolver and save that resolver, closing it later.
> support for resource paths containing workspace name
> ----------------------------------------------------
>
> Key: SLING-1447
> URL: https://issues.apache.org/jira/browse/SLING-1447
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Justin Edelson
> Assignee: Justin Edelson
> Fix For: JCR Resource 2.0.8
>
>
> via configuration, it'd be nice to be able to specify multiple workspaces.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
