[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCR-4120:
---------------------------------
Description: 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). (was: 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}}.)
> 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}}. 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).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
