[jira] [Issue Comment Deleted] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"

["Julian Reschke (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke updated JCR-4120:
--------------------------------
    Comment: was deleted

(was: trunk: [r1847167|http://svn.apache.org/r1847167] [r1846665|http://svn.apache.org/r1846665])

> 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_14
>             Fix For: 2.18, 2.16.4, 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)