Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-4120

Spi2DavexRepositoryServiceImpl always hardcodes the default workspace name to "default"

    XMLWordPrintableJSON

    Details

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                angela Angela Schreiber
                Reporter:
                kwin Konrad Windszus
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: