[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688264#comment-16688264
]
Konrad Windszus edited comment on JCR-4120 at 11/15/18 4:06 PM:
----------------------------------------------------------------
I would still argue that this is a bug being introduced by
https://issues.apache.org/jira/browse/JCR-2113 (i.e. since Jackrabbit 2.9). I
would therefore appreciate to also backport this fix to all versions which
contain JCR-2113.
was (Author: kwin):
I would still argue that this is a bug being introduced by
https://issues.apache.org/jira/browse/JCR-2113. Since that has been backported
to other jackrabbit versions I would also appreciate to also backport this fix.
> Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to
> "default"
> ---------------------------------------------------------------------------------------
>
> Key: JCR-4120
> URL: https://issues.apache.org/jira/browse/JCR-4120
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-spi2dav
> Reporter: Konrad Windszus
> Assignee: angela
> Priority: Major
> Fix For: 2.18, 2.17.7
>
>
> Basically the patch from JCR-2113 breaks the default workspace handling when
> the {{org.apache.jackrabbit.spi2davex.Spi2davexRepositoryServiceFactory}} is
> being used, because it always assumes that the default workspace name is
> {{default}}. This is unfortunately not always true. The only reason why the
> default workspace name need to be passed at all seems to be backwards
> compatibility (prior to version 1.5 this was mandatory, see JCR-1842).
> Unfortunately the assumed default workspace name being {{default}} may lead
> to issues, as this is then used to with each call to
> {{org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.obtain(...)}} where it
> falls back to the default workspace name when no explicit workspace name is
> given.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
