[
https://issues.apache.org/jira/browse/JCRVLT-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901395#comment-15901395
]
Konrad Windszus edited comment on JCRVLT-144 at 3/8/17 3:24 PM:
----------------------------------------------------------------
In SLING-6618 we ran into the same issue, which is unfortunately not solved by
the workaround
(https://github.com/apache/jackrabbit-filevault/blob/trunk/vault-davex/src/main/java/org/apache/jackrabbit/vault/davex/DAVExRepositoryFactory.java#L105).
Passing the empty string leads to the empty string being used in
https://github.com/apache/jackrabbit/blob/60f44f7d5c67c869ab4dbc7b620c5b7183a0423d/jackrabbit-spi2dav/src/main/java/org/apache/jackrabbit/spi2davex/Spi2davexRepositoryServiceFactory.java#L128.
Which in turn leads to using the empty string in
https://github.com/apache/jackrabbit/blob/60f44f7d5c67c869ab4dbc7b620c5b7183a0423d/jackrabbit-spi2dav/src/main/java/org/apache/jackrabbit/spi2davex/RepositoryServiceImpl.java#L307
which doesn't seem valid and throws the exception in
https://github.com/apache/jackrabbit/blob/60f44f7d5c67c869ab4dbc7b620c5b7183a0423d/jackrabbit-spi2dav/src/main/java/org/apache/jackrabbit/spi2dav/RepositoryServiceImpl.java#L783.
IMHO it must be possible to use {{null}} as workspace name, which is no longer
possible due to the changes in JCR-2113.
was (Author: kwin):
In SLING-6618 we ran into the same issue, which is unfortunately not solved by
the workaround
(https://github.com/apache/jackrabbit-filevault/blob/trunk/vault-davex/src/main/java/org/apache/jackrabbit/vault/davex/DAVExRepositoryFactory.java#L105).
Passing the empty string leads to the empty string being used in
https://github.com/apache/jackrabbit/blob/60f44f7d5c67c869ab4dbc7b620c5b7183a0423d/jackrabbit-spi2dav/src/main/java/org/apache/jackrabbit/spi2davex/Spi2davexRepositoryServiceFactory.java#L128.
Which in turn leads to using the empty string in
https://github.com/apache/jackrabbit/blob/60f44f7d5c67c869ab4dbc7b620c5b7183a0423d/jackrabbit-spi2dav/src/main/java/org/apache/jackrabbit/spi2davex/RepositoryServiceImpl.java#L307
which doesn't seem valid and throws the exception in
https://github.com/apache/jackrabbit/blob/60f44f7d5c67c869ab4dbc7b620c5b7183a0423d/jackrabbit-spi2dav/src/main/java/org/apache/jackrabbit/spi2dav/RepositoryServiceImpl.java#L795.
IMHO it must be possible to use {{null}} as workspace name, which is no longer
possible due to the changes in JCR-2113.
> Unable to perform checkout due to wrong default workspace handling
> ------------------------------------------------------------------
>
> Key: JCRVLT-144
> URL: https://issues.apache.org/jira/browse/JCRVLT-144
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Affects Versions: 3.1.28, 3.1.30
> Reporter: Radu Cotescu
> Assignee: Tobias Bocanegra
> Fix For: 3.1.36
>
>
> When trying to perform a {{vlt co}} with {{vlt}} > 3.1.26 I get the following
> error message:
> {noformat}
> vlt co --force http://localhost:4502
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m;
> support was removed in 8.0
> Checkout http://localhost:4502/crx/server/-/jcr:root/ with local files using
> root at [...]/content/src/content/jcr_root
> Connecting via JCR remoting to http://localhost:4502/crx/server
> [ERROR] checkout: org.apache.jackrabbit.vault.vlt.VltException: Unable to
> mount filesystem
> caused by: javax.jcr.lock.LockException: Precondition Failed
> caused by: org.apache.jackrabbit.webdav.DavException: Precondition Failed
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
