You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2017/03/08 07:06:38 UTC

[jira] [Commented] (SLING-6618) Specify crx.default as workspace for AEM servers

    [ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900817#comment-15900817 ] 

Konrad Windszus commented on SLING-6618:
----------------------------------------

I think the relevant workaround from VLT was implemented in https://fisheye.apache.org/browse/jackrabbit/commons/filevault/trunk/vault-davex/src/main/java/org/apache/jackrabbit/vault/davex/DAVExRepositoryFactory.java?u=-1&r1=1765204&r2=1775225. Either that is not working or does not apply here. In case of the former, please reopen the JCRVLT-144. Just hardcoding the default workspace  doesn't sound like a good solution. 

The original cause for the issue seems to be in https://github.com/apache/jackrabbit/blame/60f44f7d5c67c869ab4dbc7b620c5b7183a0423d/jackrabbit-spi2dav/src/main/java/org/apache/jackrabbit/spi2davex/Spi2davexRepositoryServiceFactory.java#L92. I think it would be worthwhile to debug a littlebit deeper (and set a breakpoint in Spi2davexRepositoryServiceFactory) to see what the real issue is.


> Specify crx.default as workspace for AEM servers
> ------------------------------------------------
>
>                 Key: SLING-6618
>                 URL: https://issues.apache.org/jira/browse/SLING-6618
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.10
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>         Attachments: SLING-6618.patch
>
>
> The current impl-vlt does try to connect to two different repository urls - one for sling and one for crx. In the case of the latter, it apparently needs to subsequently give the default workspace name (crx.default) to the login method - otherwise, trying to connect to the AEM server fails with "precondition failed" messages.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)