jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
Date Mon, 13 Mar 2017 09:36:04 GMT

    [ https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907081#comment-15907081

Konrad Windszus commented on JCR-4120:

Basically the comment in https://issues.apache.org/jira/browse/JCR-2113?focusedCommentId=15760326&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15760326
asks about why the default behaviour has been changed, and it seems, this was by mistake.

> 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
>    Affects Versions: 2.9.1
>            Reporter: Konrad Windszus
> 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}}. Instead
it must rather make no assumptions about the default workspace name and should instead just
use {{null}}.

This message was sent by Atlassian JIRA

View raw message