[ https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688341#comment-16688341 ]
Julian Reschke edited comment on JCR-4120 at 11/15/18 4:53 PM: --------------------------------------------------------------- I agree - changing the default for the workspace seems to be unrelated to "JSR 283 Access Control Management" (JCR-2113). Thus we should simply restore the correct behavior in the affected branches. (changed back to "minor bug" and marked for backport) was (Author: reschke): I agree - changing the default for the workspace seems to be unrelated to "JSR 283 Access Control Management" (JCR-2113). Thus we should simply restore the correct behavior in the affected branches. > 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: Bug > Components: jackrabbit-spi2dav > Reporter: Konrad Windszus > Assignee: angela > Priority: Minor > Labels: candidate_jcr_2_16 > 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)