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

["Karl Pauls (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls updated SLING-6618:
------------------------------
    Attachment: SLING-6618.patch

I attached [^SLING-6618.patch] that makes impl-vlt use crx.default as workspace when connected to a crx server. There shouldn't be any downside doing it this way and it makes things work without problems with current AEM servers. 

However, I think it is somewhat strange that it isn't able to determine that this is the default server by itself. I found JCRVLT-144 which sounded like it would address exactly this issue and I updated IDE to the latest jackrabbit svn version but it didn't fix the issue completely (stopped saying "precondition failed" but started saying unknown default workspace ''). 

Ultimately, this patch makes it work for now and it might be a start to later on provide a way to specify a workspace different from the default (if that is ever desired). 

I can commit the patch but I would like to get some feedback first if it makes sense (and obviously, whether I'm just missing something) - hence, WDYT? 

> 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)