[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4120:
Fix Version/s: 2.14.7
> 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.14.7, 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4120:
Labels: (was: candidate_jcr_2_14)
> 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
> Fix For: 2.18, 2.16.4, 2.14.7, 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4120:
Fix Version/s: 2.16.4
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4120:
Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16)
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4120:
Priority: Minor (was: Major)
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4120:
Labels: candidate_jcr_2_16 (was: )
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4120:
Issue Type: Bug (was: Improvement)
> 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: Major
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-4120:
Priority: Major (was: Minor)
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-4120:
Labels: (was: candidate_jcr_2_16)
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-4120:
Issue Type: Improvement (was: Bug)
> 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: Minor
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-4120:
Priority: Minor (was: Major)
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-4120:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed revision 1846665.
I committed the changes to 'Spi2davexRepositoryServiceFactory' with slightly
modified comments in particular also linking to JCR-4120 as for any setup with
jcrserver <1.5 this modification is most probably a breaking change.
in terms of testing: i ran the ConformanceTest present with
_jackrabbit-jcr2dav_ and all executed tests passed with no default workspace
name set in the factory (verified that this code is actually executed).
> 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: Major
> Fix For: 2.18
>
>
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4120:
Fix Version/s: 2.18
> 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
>Priority: Major
> Fix For: 2.18
>
>
> 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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4120:
Affects Version/s: (was: 2.9.1)
> 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
>
> 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
(v6.3.15#6346)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCR-4120:
-
Status: Patch Available (was: Open)
> 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).
> 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
(v6.3.15#6346)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
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). 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. (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}}.
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).)
> 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).
> 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
(v6.3.15#6346)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
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)
[jira] [Updated] (JCR-4120) Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"
[
https://issues.apache.org/jira/browse/JCR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCR-4120:
-
Affects Version/s: 2.9.1
> 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
(v6.3.15#6346)
