[JCR-4120] Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.18, 2.16.4, 2.14.7, 2.17.7
• Component/s: jackrabbit-spi2dav
• Assignee: Angela Schreiber
• Reporter: Konrad Windszus
• Created: 13/Mar/17 09:34
• Updated: 17/Jul/20 11:17
• Resolved: 15/Nov/18 15:38

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.

Issue Links

• blocks: SLING-6618 Specify crx.default as workspace for AEM servers
• is broken by: JCR-2113 JSR 283 Access Control Management
• is related to: JCRVLT-144 Unable to perform checkout due to wrong default workspace handling
• relates to: JCR-1842 SPI: RepositoryService.obtain should allow to pass null workspaceName indicating the default workspace
• links to: GitHub Pull Request #51
• links to: GitHub Pull Request #51