[jira] [Resolved] (SLING-5292) Provide Composum feature
[
https://issues.apache.org/jira/browse/SLING-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-5292.
-
Resolution: Done
composum-sling-core-* 1.3.1 now on Maven Central
r1714428
> Provide Composum feature
>
>
> Key: SLING-5292
> URL: https://issues.apache.org/jira/browse/SLING-5292
> Project: Sling
> Issue Type: Task
> Components: Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Launchpad Karaf Features 0.2.0, Launchpad Karaf
> Integration Tests 0.2.0
>
>
> {noformat}
>
>
>
> mvn:com.composum.sling.core/composum-sling-core-commons/1.4.0-SNAPSHOT
>
> mvn:com.composum.sling.core/composum-sling-core-console/1.4.0-SNAPSHOT
>
> mvn:com.composum.sling.core/composum-sling-core-jslibs/1.4.0-SNAPSHOT
>
> sling
> dependency="true">mvn:org.apache.commons/commons-lang3/3.4
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SLING-5292) Provide Composum feature
[
https://issues.apache.org/jira/browse/SLING-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15005843#comment-15005843
]
Oliver Lietz edited comment on SLING-5292 at 11/15/15 6:05 PM:
---
composum-sling-core-* 1.3.1 now on Maven Central
r1714428
r1714480
was (Author: olli):
composum-sling-core-* 1.3.1 now on Maven Central
r1714428
> Provide Composum feature
>
>
> Key: SLING-5292
> URL: https://issues.apache.org/jira/browse/SLING-5292
> Project: Sling
> Issue Type: Task
> Components: Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Launchpad Karaf Features 0.2.0, Launchpad Karaf
> Integration Tests 0.2.0
>
>
> {noformat}
>
>
>
> mvn:com.composum.sling.core/composum-sling-core-commons/1.4.0-SNAPSHOT
>
> mvn:com.composum.sling.core/composum-sling-core-console/1.4.0-SNAPSHOT
>
> mvn:com.composum.sling.core/composum-sling-core-jslibs/1.4.0-SNAPSHOT
>
> sling
> sling-jcr
> sling-scripting-jsp
> dependency="true">mvn:org.apache.commons/commons-lang3/3.4
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-5219) Mounting a ResourceProvider makes it impossible to create child resources under it
[
https://issues.apache.org/jira/browse/SLING-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-5219:
Fix Version/s: Servlets POST 2.3.10
> Mounting a ResourceProvider makes it impossible to create child resources
> under it
> --
>
> Key: SLING-5219
> URL: https://issues.apache.org/jira/browse/SLING-5219
> Project: Sling
> Issue Type: Bug
> Components: Servlets
>Affects Versions: Servlets Post 2.3.6
>Reporter: Robert Munteanu
> Fix For: Servlets POST 2.3.10
>
>
> (I am not sure where the problem is exactly, but setting it under Servlets
> POST for now ).
> Consider the following scenario:
> * JCR provider mounted at {{/}}
> * FS provider mounted at {{/content/blog/images}}
> * No resources in the JCR repo for {{/content}} or {{/content/blog}}
> A POST call to create {{/content}} or {{/content/blog}} ( I have used
> [httpie|https://github.com/jkbrzt/httpie] ) fails {noformat}http
> --auth=admin:admin -f POST http://localhost:8080 /content
> 'sling\:target=/content/blog/posts'{noformat}
> If I remove the FS provider then the call succeeds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-5219) Mounting a ResourceProvider makes it impossible to create child resources under it
[
https://issues.apache.org/jira/browse/SLING-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-5219:
Priority: Blocker (was: Major)
> Mounting a ResourceProvider makes it impossible to create child resources
> under it
> --
>
> Key: SLING-5219
> URL: https://issues.apache.org/jira/browse/SLING-5219
> Project: Sling
> Issue Type: Bug
> Components: Servlets
>Affects Versions: Servlets Post 2.3.6
>Reporter: Robert Munteanu
>Priority: Blocker
> Fix For: Servlets POST 2.3.10
>
>
> (I am not sure where the problem is exactly, but setting it under Servlets
> POST for now ).
> Consider the following scenario:
> * JCR provider mounted at {{/}}
> * FS provider mounted at {{/content/blog/images}}
> * No resources in the JCR repo for {{/content}} or {{/content/blog}}
> A POST call to create {{/content}} or {{/content/blog}} ( I have used
> [httpie|https://github.com/jkbrzt/httpie] ) fails {noformat}http
> --auth=admin:admin -f POST http://localhost:8080 /content
> 'sling\:target=/content/blog/posts'{noformat}
> If I remove the FS provider then the call succeeds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [VOTE] Release Apache Sling Service User Mapper 1.2.2
+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Commented] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit
[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006105#comment-15006105 ] Alexander Klimetschek commented on SLING-5277: -- The patch does exactly that. In my performance tests it made a noticeable difference, since the session creation cost essentially outweighed the cache benefit. > Performance: per thread script resolver (admin session) is always created > even if cache is hit > -- > > Key: SLING-5277 > URL: https://issues.apache.org/jira/browse/SLING-5277 > Project: Sling > Issue Type: Bug > Components: Servlets >Reporter: Alexander Klimetschek > Attachments: SLING-5277.patch > > > Since SLING-3441, for every request, a new admin / privileged session is > [created in the > SlingServletResolver|https://github.com/apache/sling/blob/trunk/bundles/servlets/resolver/src/main/java/org/apache/sling/servlets/resolver/internal/SlingServletResolver.java#L532]. > It is created before the script/servlet cache is checked, so in most cases > when the cache is hit it is never used, but the cost of creating an extra > session (which can vary, especially with concurrent traffic) is incurred. > The per thread script resolver can be created lazily instead of directly in > the event to avoid this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit
[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006088#comment-15006088 ] Carsten Ziegeler commented on SLING-5277: - We can create it lazily but it needs to be created even if the resolution is coming from the cache as the script implementation might use the script resolver > Performance: per thread script resolver (admin session) is always created > even if cache is hit > -- > > Key: SLING-5277 > URL: https://issues.apache.org/jira/browse/SLING-5277 > Project: Sling > Issue Type: Bug > Components: Servlets >Reporter: Alexander Klimetschek > Attachments: SLING-5277.patch > > > Since SLING-3441, for every request, a new admin / privileged session is > [created in the > SlingServletResolver|https://github.com/apache/sling/blob/trunk/bundles/servlets/resolver/src/main/java/org/apache/sling/servlets/resolver/internal/SlingServletResolver.java#L532]. > It is created before the script/servlet cache is checked, so in most cases > when the cache is hit it is never used, but the cost of creating an extra > session (which can vary, especially with concurrent traffic) is incurred. > The per thread script resolver can be created lazily instead of directly in > the event to avoid this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Sling discovery.commons 1.0.4, discovery.base 1.1.0, discovery.oak 1.1.0 and discovery.impl 1.2.2
+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Updated] (SLING-5292) Provide Composum feature
[
https://issues.apache.org/jira/browse/SLING-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-5292:
Description:
{noformat}
mvn:com.composum.sling.core/composum-sling-core-commons/1.4.0-SNAPSHOT
mvn:com.composum.sling.core/composum-sling-core-console/1.4.0-SNAPSHOT
mvn:com.composum.sling.core/composum-sling-core-jslibs/1.4.0-SNAPSHOT
sling
sling-jcr
sling-scripting-jsp
mvn:org.apache.commons/commons-lang3/3.4
{noformat}
was:
{noformat}
mvn:com.composum.sling.core/composum-sling-core-commons/1.4.0-SNAPSHOT
mvn:com.composum.sling.core/composum-sling-core-console/1.4.0-SNAPSHOT
mvn:com.composum.sling.core/composum-sling-core-jslibs/1.4.0-SNAPSHOT
sling
mvn:org.apache.commons/commons-lang3/3.4
{noformat}
> Provide Composum feature
>
>
> Key: SLING-5292
> URL: https://issues.apache.org/jira/browse/SLING-5292
> Project: Sling
> Issue Type: Task
> Components: Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Launchpad Karaf Features 0.2.0, Launchpad Karaf
> Integration Tests 0.2.0
>
>
> {noformat}
>
>
>
> mvn:com.composum.sling.core/composum-sling-core-commons/1.4.0-SNAPSHOT
>
> mvn:com.composum.sling.core/composum-sling-core-console/1.4.0-SNAPSHOT
>
> mvn:com.composum.sling.core/composum-sling-core-jslibs/1.4.0-SNAPSHOT
>
> sling
> sling-jcr
> sling-scripting-jsp
> dependency="true">mvn:org.apache.commons/commons-lang3/3.4
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
