[jira] [Comment Edited] (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=15958509#comment-15958509
]
Konrad Windszus edited comment on SLING-6618 at 4/6/17 9:43 AM:
Some dependency have been upgraded for FileVault 3.1.38
# HttpClient 3.1 -> Http Components Client 4.5.3 (not yet in any Eclipse Orbit
repository)
# Commons Collections 3.2.1 -> Commons Collection 3.2.2
(https://issues.apache.org/jira/browse/JCRVLT-167), only available in Orbit
http://download.eclipse.org/tools/orbit/downloads/drops/R20151221205849/
# Commons IO 2.2 -> Commons IO 2.5 (not available in any Eclipse Orbit
repository yet)
# new Http Components Mime 4.5.3 (not available in any Eclipse Orbit repository
yet)
I would propose to proceed like this
# Use HttpComponents Client 4.2.6 from Eclipse Orbit instead
# Stay with Commons Collections 3.2.0 (latest in the Eclipse Orbit for Eclipse
Juno)
# Stay with Commons IO 2.2 (latest in the Eclipse Orbit)
# unclear how to deal with Http Components Mime, for now I would just embed as
library in the vlt-wrapper
There is a slight risk that those versions suffer from some bugs or are even
incompatible with FileVault, but we probably use only 10% of the FileVault
library, so I consider this risk rather low.
The other alternative would be to embed those libraries in the vlt-wrapper
[~rombert] WDYT?
was (Author: kwin):
Some dependency have been upgraded for FileVault 3.1.38
# HttpClient 3.1 -> HttpComponent Client 4.5.3 (not yet in any Eclipse Orbit
repository)
# Commons Collections 3.2.1 -> Commons Collection 3.2.2
(https://issues.apache.org/jira/browse/JCRVLT-167), only available in Orbit
http://download.eclipse.org/tools/orbit/downloads/drops/R20151221205849/
# Commons IO 2.2 -> Commons IO 2.5 (not available in any Eclipse Orbit
repository yet)
I would propose to proceed like this
# Use HttpComponents Client 4.2.6 from Eclipse Orbit instead
# Stay with Commons Collections 3.2.0 (latest in the Eclipse Orbit for Eclipse
Juno)
# Stay with Commons IO 2.2 (latest in the Eclipse Orbit)
There is a slight risk that those versions suffer from some bugs or are even
incompatible with FileVault, but we probably use only 10% of the FileVault
library, so I consider this risk rather low.
The other alternative would be to embed those libraries in the vlt-wrapper
[~rombert] 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
>Priority: Blocker
> Fix For: Sling Eclipse IDE 1.2.0
>
> 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.
> The full stack trace of the according {{RepositoryException}} looks like this
> {code}
> javax.jcr.lock.LockException: Precondition Failed
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:109)
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:51)
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:45)
> at
> org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:809)
> at
> org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:753)
> at
> org.apache.jackrabbit.spi2davex.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:307)
> at
> org.apache.jackrabbit.jcr2spi.RepositoryImpl.login(RepositoryImpl.java:151)
> at
> org.apache.jackrabbit.commons.AbstractRepository.login(AbstractRepository.java:144)
> at
> org.apache.sling.ide.jcr.RepositoryUtils.getRepositoryAddress(RepositoryUtils.java:84)
> at
> org.apache.sling.ide.jcr.RepositoryUtils.getRepository(RepositoryUtils.java:44)
> at
> org.apache.sling.ide.impl.vlt.VltRepository.connect(VltRepository.java:70)
> at
> org.apache.sling.ide.impl.vlt.VltRepositoryFactory.connectRepository(VltRepositoryFactory.java:69)
> at
> org.apache.sling.ide.eclipse.core.ServerUtil.connectRepository(ServerUtil.java:146)
> at
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.start(SlingLaunchpadBehaviour.java:95)
> at
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadLaunchConfigur
[jira] [Comment Edited] (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=15958509#comment-15958509
]
Konrad Windszus edited comment on SLING-6618 at 4/6/17 8:05 AM:
Some dependency have been upgraded for FileVault 3.1.38
# HttpClient 3.1 -> HttpComponent Client 4.5.3 (not yet in any Eclipse Orbit
repository)
# Commons Collections 3.2.1 -> Commons Collection 3.2.2
(https://issues.apache.org/jira/browse/JCRVLT-167), only available in Orbit
http://download.eclipse.org/tools/orbit/downloads/drops/R20151221205849/
# Commons IO 2.2 -> Commons IO 2.5 (not available in any Eclipse Orbit
repository yet)
I would propose to proceed like this
# Use HttpComponents Client 4.2.6 from Eclipse Orbit instead
# Stay with Commons Collections 3.2.0 (latest in the Eclipse Orbit for Eclipse
Juno)
# Stay with Commons IO 2.2 (latest in the Eclipse Orbit)
There is a slight risk that those versions suffer from some bugs or are even
incompatible with FileVault, but we probably use only 10% of the FileVault
library, so I consider this risk rather low.
The other alternative would be to embed those libraries in the vlt-wrapper
[~rombert] WDYT?
was (Author: kwin):
Some dependency have been upgraded for FileVault 3.1.38
# HttpClient 3.1 -> HttpComponent Client 4.5.3 (not yet in any Eclipse Orbit
repository)
# Commons Collections 3.2.1 -> Commons Collection 3.2.2
(https://issues.apache.org/jira/browse/JCRVLT-167), only available in Orbit
http://download.eclipse.org/tools/orbit/downloads/drops/R20151221205849/
# Commons IO 2.2 -> Commons IO 2.5 (not available in any Eclipse Orbit
repository yet)
I would propose to proceed like this
# Use HttpComponents Client 4.2.6 from Eclipse Orbit instead
# Stay with Commons Collections 3.2.0 (latest in the Eclipse Orbit for Eclipse
Juno)
# Stay with Commons IO 2.2 (latest in the Eclipse Orbit)
The other alternative would be to embed those libraries in the vlt-wrapper
[~rombert] 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
>Priority: Blocker
> Fix For: Sling Eclipse IDE 1.2.0
>
> 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.
> The full stack trace of the according {{RepositoryException}} looks like this
> {code}
> javax.jcr.lock.LockException: Precondition Failed
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:109)
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:51)
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:45)
> at
> org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:809)
> at
> org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:753)
> at
> org.apache.jackrabbit.spi2davex.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:307)
> at
> org.apache.jackrabbit.jcr2spi.RepositoryImpl.login(RepositoryImpl.java:151)
> at
> org.apache.jackrabbit.commons.AbstractRepository.login(AbstractRepository.java:144)
> at
> org.apache.sling.ide.jcr.RepositoryUtils.getRepositoryAddress(RepositoryUtils.java:84)
> at
> org.apache.sling.ide.jcr.RepositoryUtils.getRepository(RepositoryUtils.java:44)
> at
> org.apache.sling.ide.impl.vlt.VltRepository.connect(VltRepository.java:70)
> at
> org.apache.sling.ide.impl.vlt.VltRepositoryFactory.connectRepository(VltRepositoryFactory.java:69)
> at
> org.apache.sling.ide.eclipse.core.ServerUtil.connectRepository(ServerUtil.java:146)
> at
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.start(SlingLaunchpadBehaviour.java:95)
> at
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadLaunchConfigurationDelegate.launch(SlingLaunchpadLaunchConfigurationDelegate.java:45)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at
>
[jira] [Comment Edited] (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=15907111#comment-15907111
]
Konrad Windszus edited comment on SLING-6618 at 3/13/17 10:26 AM:
--
[~karlpauls] The workaround is quite verbose as it requires to always use the
workspace name with {{Repository.login}} (although the default should be used
everywhere). For the short-term I would rather like to rely on the workaround
from
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
which allows to pass in a default workspace name. That would be extracted from
the URI. That way the fix would just be a one-liner in {{RepositoryUtils}} for
the constant {{WEBDAV_URL_LOCATIONS}}:
{{crx/-/jcr:root}} would just become {{crx/crx.default/jcr:root}}.
So instead of applying the fix as is I would wait for the next FileVault
release (Vote going on in
http://www.mail-archive.com/dev@jackrabbit.apache.org/msg37864.html) and then
just modify the {{WEBDAV_URL_LOCATIONS}}.
I think the right long-term fix would be
https://issues.apache.org/jira/browse/JCR-4120. Maybe you can try to push for
that a bit, so this is part of the next Jackrabbit release and can subsequently
be integrated in Jackrabbit FileVault.
was (Author: kwin):
[~karlpauls] The workaround is quite verbose as it requires to always use the
workspace name with {{Repository.login}} (although the default should be used
everywhere). For the midterm I would rather like to rely on the workaround from
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
which allows to pass in a default workspace name. That would be extracted from
the URI. That way the fix would just be a one-liner in {{RepositoryUtils}} for
the constant {{WEBDAV_URL_LOCATIONS}}:
{{crx/-/jcr:root}} would just become {{crx/crx.default/jcr:root}}.
I think the right long-term fix would be
https://issues.apache.org/jira/browse/JCR-4120. Maybe you can try to push for
that a bit, so this is part of the next Jackrabbit release and can subsequently
be integrated in Jackrabbit FileVault.
> 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
> Fix For: Sling Eclipse IDE 1.2.0
>
> 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.
> The full stack trace of the according {{RepositoryException}} looks like this
> {code}
> javax.jcr.lock.LockException: Precondition Failed
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:109)
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:51)
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:45)
> at
> org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:809)
> at
> org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:753)
> at
> org.apache.jackrabbit.spi2davex.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:307)
> at
> org.apache.jackrabbit.jcr2spi.RepositoryImpl.login(RepositoryImpl.java:151)
> at
> org.apache.jackrabbit.commons.AbstractRepository.login(AbstractRepository.java:144)
> at
> org.apache.sling.ide.jcr.RepositoryUtils.getRepositoryAddress(RepositoryUtils.java:84)
> at
> org.apache.sling.ide.jcr.RepositoryUtils.getRepository(RepositoryUtils.java:44)
> at
> org.apache.sling.ide.impl.vlt.VltRepository.connect(VltRepository.java:70)
> at
> org.apache.sling.ide.impl.vlt.VltRepositoryFactory.connectRepository(VltRepositoryFactory.java:69)
> at
> org.apache.sling.ide.eclipse.core.ServerUtil.connectRepository(ServerUtil.java:146)
> at
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.start(SlingLaunchpadBehaviour.java:95)
> at
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadLaunchConfigurationDelegate.launch(SlingLaunchpadLaunchConfigurationDelegate.java:45)
> at
>
[jira] [Comment Edited] (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=15907111#comment-15907111
]
Konrad Windszus edited comment on SLING-6618 at 3/13/17 10:24 AM:
--
[~karlpauls] The workaround is quite verbose as it requires to always use the
workspace name with {{Repository.login}} (although the default should be used
everywhere). For the midterm I would rather like to rely on the workaround from
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
which allows to pass in a default workspace name. That would be extracted from
the URI. That way the fix would just be a one-liner in {{RepositoryUtils}} for
the constant {{WEBDAV_URL_LOCATIONS}}:
{{crx/-/jcr:root}} would just become {{crx/crx.default/jcr:root}}.
I think the right long-term fix would be
https://issues.apache.org/jira/browse/JCR-4120. Maybe you can try to push for
that a bit, so this is part of the next Jackrabbit release and can subsequently
be integrated in Jackrabbit FileVault.
was (Author: kwin):
[~karlpauls] The workaround is quite verbose as it requires to always use the
workspace name with {{Repository.login}} (although the default should be used
everywhere). I think the right upstream fix would be
https://issues.apache.org/jira/browse/JCR-4120. Maybe you can try to push for
that a bit, so this is part of the next Jackrabbit release and can subsequently
be integrated in Jackrabbit FileVault.
> 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
> Fix For: Sling Eclipse IDE 1.2.0
>
> 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.
> The full stack trace of the according {{RepositoryException}} looks like this
> {code}
> javax.jcr.lock.LockException: Precondition Failed
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:109)
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:51)
> at
> org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:45)
> at
> org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:809)
> at
> org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:753)
> at
> org.apache.jackrabbit.spi2davex.RepositoryServiceImpl.obtain(RepositoryServiceImpl.java:307)
> at
> org.apache.jackrabbit.jcr2spi.RepositoryImpl.login(RepositoryImpl.java:151)
> at
> org.apache.jackrabbit.commons.AbstractRepository.login(AbstractRepository.java:144)
> at
> org.apache.sling.ide.jcr.RepositoryUtils.getRepositoryAddress(RepositoryUtils.java:84)
> at
> org.apache.sling.ide.jcr.RepositoryUtils.getRepository(RepositoryUtils.java:44)
> at
> org.apache.sling.ide.impl.vlt.VltRepository.connect(VltRepository.java:70)
> at
> org.apache.sling.ide.impl.vlt.VltRepositoryFactory.connectRepository(VltRepositoryFactory.java:69)
> at
> org.apache.sling.ide.eclipse.core.ServerUtil.connectRepository(ServerUtil.java:146)
> at
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.start(SlingLaunchpadBehaviour.java:95)
> at
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadLaunchConfigurationDelegate.launch(SlingLaunchpadLaunchConfigurationDelegate.java:45)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at
> org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
> at
> org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
> at
> org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: org.apache.jackrabbit.webdav.DavException: Precondition Failed
> at
> org.apache.jackrabbit.webdav.cli
[jira] [Comment Edited] (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=15901170#comment-15901170
]
Konrad Windszus edited comment on SLING-6618 at 3/8/17 12:26 PM:
-
The reason why in AEM the default workspace name is {{crx.default}} is in
com.adobe.granite.repository.impl.SlingRepositoryManager() which internally
calls {{Jcr.with("crx.default")}}
(http://static.javadoc.io/org.apache.jackrabbit/oak-jcr/1.6.0/org/apache/jackrabbit/oak/jcr/Jcr.html#with(java.lang.String).
But basically whenever the workspace name is {{null}} for
{{Repository.login(...)}} calls it should act on the default workspace (compare
with
https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Repository.html#login(javax.jcr.Credentials,%20java.lang.String)).
This currently does not seem to be the case, while Sling IDE itself only calls
{{org.apache.jackrabbit.vault.davex.DAVExRepositoryFactory}} this does not seem
to correctly resolve to the correct default workspace. Basically that should
pass {{null}} as {{workspaceName}} in
https://github.com/apache/jackrabbit/blob/60f44f7d5c67c869ab4dbc7b620c5b7183a0423d/jackrabbit-spi2dav/src/main/java/org/apache/jackrabbit/spi2davex/Spi2davexRepositoryServiceFactory.java#L128
which is currently not possible, because that is either any explicit String
being set or just the empty string, but never null.
was (Author: kwin):
The reason why in AEM the default workspace name is {{crx.default}} is in
com.adobe.granite.repository.impl.SlingRepositoryManager() which internally
calls {{Jcr.with("crx.default")}}
(http://static.javadoc.io/org.apache.jackrabbit/oak-jcr/1.6.0/org/apache/jackrabbit/oak/jcr/Jcr.html#with(java.lang.String).
But basically whenever the workspace name is {{null}} for
{{Repository.login(...)}} calls it should act on the default workspace (compare
with
https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Repository.html#login(javax.jcr.Credentials,%20java.lang.String)).
This currently does not seem to be the case, while Sling IDE itself only calls
{{org.apache.jackrabbit.vault.davex.DAVExRepositoryFactory}} this does not seem
to correctly resolve to the correct default workspace.
> 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
> Fix For: Sling Eclipse IDE 1.2.0
>
> 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)
[jira] [Comment Edited] (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=15901170#comment-15901170
]
Konrad Windszus edited comment on SLING-6618 at 3/8/17 12:20 PM:
-
The reason why in AEM the default workspace name is {{crx.default}} is in
com.adobe.granite.repository.impl.SlingRepositoryManager() which internally
calls {{Jcr.with("crx.default")}}
(http://static.javadoc.io/org.apache.jackrabbit/oak-jcr/1.6.0/org/apache/jackrabbit/oak/jcr/Jcr.html#with(java.lang.String).
But basically whenever the workspace name is {{null}} for
{{Repository.login(...)}} calls it should act on the default workspace (compare
with
https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Repository.html#login(javax.jcr.Credentials,%20java.lang.String)).
This currently does not seem to be the case, while Sling IDE itself only calls
{{org.apache.jackrabbit.vault.davex.DAVExRepositoryFactory}} this does not seem
to correctly resolve to the correct default workspace.
was (Author: kwin):
The reason why in AEM the default workspace name is {{crx.default}} is in
com.adobe.granite.repository.impl.SlingRepositoryManager() which internally
calls {{Jcr.with("crx.default")}}
(http://static.javadoc.io/org.apache.jackrabbit/oak-jcr/1.6.0/org/apache/jackrabbit/oak/jcr/Jcr.html#with(java.lang.String).
But basically whenever the workspace name is {{null}} for
{{Repository.login(...)}} calls it should act on the default workspace (compare
with
https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Repository.html#login(javax.jcr.Credentials,%20java.lang.String)).
This currently does not seem to be the case.
> 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
> Fix For: Sling Eclipse IDE 1.2.0
>
> 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)
