[jira] [Created] (SLING-2492) add documentation on SlingPostServlet's post processor
Nicolas Peltier created SLING-2492: -- Summary: add documentation on SlingPostServlet's post processor Key: SLING-2492 URL: https://issues.apache.org/jira/browse/SLING-2492 Project: Sling Issue Type: Wish Components: Documentation Reporter: Nicolas Peltier Priority: Minor I've started a documentation on https://cwiki.apache.org/confluence/display/SLING/Creating+a+SlingPostServlet+post+processor for integration in http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SLING-2726) allow wildcards in servlet paths
Nicolas Peltier created SLING-2726: -- Summary: allow wildcards in servlet paths Key: SLING-2726 URL: https://issues.apache.org/jira/browse/SLING-2726 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Nicolas Peltier Priority: Minor this would be nice to allow minimum wildcard for servlet paths, i.e. /a/b/* (no suffix), as some use cases can't be cover right now with jcr based resources + path servlets. Basically every resource model where you don't need a jcr node for (while it's very convenient most of the time). I'm thinking for example of having a profile servlet with a nice public /profile/jdoe.html url. Right now my possibilities are * to create a flat tree of fake user nodes under a profile node just for the sake of my urls (don't need righs handling, don't need other verbs for the same resource), * to have tons of vanityUrls (not meant for that kind of usage) * to create my own ResourceProvider that map that kind of URLs to existing jcr resources. * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe And i tend to think a tiny wildcard in a path parameter would be nicer :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2726) allow simple wildcards in servlet paths
[ https://issues.apache.org/jira/browse/SLING-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-2726: --- Description: While i'm a big fan/evangelist of sling unique servlet management. I tend to think this would be nice to allow minimum wildcard for servlet paths, i.e. /a/b/* (no suffix), as some use cases can't be cover right now with jcr based resources + path servlets. Basically every resource model where you don't need a jcr node for (while it's very convenient most of the time). I'm thinking for example of having a profile servlet with a nice public /profile/jdoe.html url. Right now my possibilities are * to create a flat tree of fake user nodes under a profile node just for the sake of my urls (don't need righs handling, don't need other verbs for the same resource), * to have tons of vanityUrls (not meant for that kind of usage) * to create my own ResourceProvider that map that kind of URLs to existing jcr resources. * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe And i tend to think a tiny wildcard in a path parameter would be nicer :-) was: this would be nice to allow minimum wildcard for servlet paths, i.e. /a/b/* (no suffix), as some use cases can't be cover right now with jcr based resources + path servlets. Basically every resource model where you don't need a jcr node for (while it's very convenient most of the time). I'm thinking for example of having a profile servlet with a nice public /profile/jdoe.html url. Right now my possibilities are * to create a flat tree of fake user nodes under a profile node just for the sake of my urls (don't need righs handling, don't need other verbs for the same resource), * to have tons of vanityUrls (not meant for that kind of usage) * to create my own ResourceProvider that map that kind of URLs to existing jcr resources. * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe And i tend to think a tiny wildcard in a path parameter would be nicer :-) Summary: allow simple wildcards in servlet paths (was: allow wildcards in servlet paths) allow simple wildcards in servlet paths --- Key: SLING-2726 URL: https://issues.apache.org/jira/browse/SLING-2726 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Nicolas Peltier Priority: Minor While i'm a big fan/evangelist of sling unique servlet management. I tend to think this would be nice to allow minimum wildcard for servlet paths, i.e. /a/b/* (no suffix), as some use cases can't be cover right now with jcr based resources + path servlets. Basically every resource model where you don't need a jcr node for (while it's very convenient most of the time). I'm thinking for example of having a profile servlet with a nice public /profile/jdoe.html url. Right now my possibilities are * to create a flat tree of fake user nodes under a profile node just for the sake of my urls (don't need righs handling, don't need other verbs for the same resource), * to have tons of vanityUrls (not meant for that kind of usage) * to create my own ResourceProvider that map that kind of URLs to existing jcr resources. * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe And i tend to think a tiny wildcard in a path parameter would be nicer :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2726) allow simple wildcards in servlet paths
[ https://issues.apache.org/jira/browse/SLING-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13575722#comment-13575722 ] Nicolas Peltier commented on SLING-2726: I see. Wouldn't that be possible to add resource tree as a possible resource type (in addition to servlets and jcr based resource)? A jcr based resource, that handles every descendent? allow simple wildcards in servlet paths --- Key: SLING-2726 URL: https://issues.apache.org/jira/browse/SLING-2726 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Nicolas Peltier Priority: Minor While i'm a big fan/evangelist of sling unique servlet management. I tend to think this would be nice to allow minimum wildcard for servlet paths, i.e. /a/b/* (no suffix), as some use cases can't be cover right now with jcr based resources + path servlets. Basically every resource model where you don't need a jcr node for (while it's very convenient most of the time). I'm thinking for example of having a profile servlet with a nice public /profile/jdoe.html url. Right now my possibilities are * to create a flat tree of fake user nodes under a profile node just for the sake of my urls (don't need righs handling, don't need other verbs for the same resource), * to have tons of vanityUrls (not meant for that kind of usage) * to create my own ResourceProvider that map that kind of URLs to existing jcr resources. * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe And i tend to think a tiny wildcard in a path parameter would be nicer :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2726) allow simple wildcards in servlet paths
[ https://issues.apache.org/jira/browse/SLING-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13576497#comment-13576497 ] Nicolas Peltier commented on SLING-2726: have a specific node type on which you can't add any children, let say /a/b/c is of that type. then /a/b/c(/*)? would be handled by c's renderer. allow simple wildcards in servlet paths --- Key: SLING-2726 URL: https://issues.apache.org/jira/browse/SLING-2726 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Nicolas Peltier Priority: Minor While i'm a big fan/evangelist of sling unique servlet management. I tend to think this would be nice to allow minimum wildcard for servlet paths, i.e. /a/b/* (no suffix), as some use cases can't be cover right now with jcr based resources + path servlets. Basically every resource model where you don't need a jcr node for (while it's very convenient most of the time). I'm thinking for example of having a profile servlet with a nice public /profile/jdoe.html url. Right now my possibilities are * to create a flat tree of fake user nodes under a profile node just for the sake of my urls (don't need righs handling, don't need other verbs for the same resource), * to have tons of vanityUrls (not meant for that kind of usage) * to create my own ResourceProvider that map that kind of URLs to existing jcr resources. * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe And i tend to think a tiny wildcard in a path parameter would be nicer :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (SLING-2726) allow simple wildcards in servlet paths
[ https://issues.apache.org/jira/browse/SLING-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13576522#comment-13576522 ] Nicolas Peltier edited comment on SLING-2726 at 2/12/13 10:21 AM: -- yes, but then it's not the same handling to have /a/b/c.html/d and /a/b/c/d.html (url form cache layers). Would my proposal cause a lot of issues? was (Author: npeltier): yes, but then it's not the same handling to have /a/b/c.html/d and /a/b/c/d.html (url form cache layers) allow simple wildcards in servlet paths --- Key: SLING-2726 URL: https://issues.apache.org/jira/browse/SLING-2726 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Nicolas Peltier Priority: Minor While i'm a big fan/evangelist of sling unique servlet management. I tend to think this would be nice to allow minimum wildcard for servlet paths, i.e. /a/b/* (no suffix), as some use cases can't be cover right now with jcr based resources + path servlets. Basically every resource model where you don't need a jcr node for (while it's very convenient most of the time). I'm thinking for example of having a profile servlet with a nice public /profile/jdoe.html url. Right now my possibilities are * to create a flat tree of fake user nodes under a profile node just for the sake of my urls (don't need righs handling, don't need other verbs for the same resource), * to have tons of vanityUrls (not meant for that kind of usage) * to create my own ResourceProvider that map that kind of URLs to existing jcr resources. * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe And i tend to think a tiny wildcard in a path parameter would be nicer :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2726) allow simple wildcards in servlet paths
[ https://issues.apache.org/jira/browse/SLING-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13576522#comment-13576522 ] Nicolas Peltier commented on SLING-2726: yes, but then it's not the same handling to have /a/b/c.html/d and /a/b/c/d.html (url form cache layers) allow simple wildcards in servlet paths --- Key: SLING-2726 URL: https://issues.apache.org/jira/browse/SLING-2726 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Nicolas Peltier Priority: Minor While i'm a big fan/evangelist of sling unique servlet management. I tend to think this would be nice to allow minimum wildcard for servlet paths, i.e. /a/b/* (no suffix), as some use cases can't be cover right now with jcr based resources + path servlets. Basically every resource model where you don't need a jcr node for (while it's very convenient most of the time). I'm thinking for example of having a profile servlet with a nice public /profile/jdoe.html url. Right now my possibilities are * to create a flat tree of fake user nodes under a profile node just for the sake of my urls (don't need righs handling, don't need other verbs for the same resource), * to have tons of vanityUrls (not meant for that kind of usage) * to create my own ResourceProvider that map that kind of URLs to existing jcr resources. * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe And i tend to think a tiny wildcard in a path parameter would be nicer :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2726) allow simple wildcards in servlet paths
[ https://issues.apache.org/jira/browse/SLING-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577551#comment-13577551 ] Nicolas Peltier commented on SLING-2726: What i like with jcr based one vs. http service is i have ACLs management for free. I can still connect to the repo in my service and test my rights against a JCR node. @Alex, interesting approach, will look into that. ok, looks like this bug can be closed. May be another one for easily creating ResourceProvider should be done? allow simple wildcards in servlet paths --- Key: SLING-2726 URL: https://issues.apache.org/jira/browse/SLING-2726 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Nicolas Peltier Priority: Minor While i'm a big fan/evangelist of sling unique servlet management. I tend to think this would be nice to allow minimum wildcard for servlet paths, i.e. /a/b/* (no suffix), as some use cases can't be cover right now with jcr based resources + path servlets. Basically every resource model where you don't need a jcr node for (while it's very convenient most of the time). I'm thinking for example of having a profile servlet with a nice public /profile/jdoe.html url. Right now my possibilities are * to create a flat tree of fake user nodes under a profile node just for the sake of my urls (don't need righs handling, don't need other verbs for the same resource), * to have tons of vanityUrls (not meant for that kind of usage) * to create my own ResourceProvider that map that kind of URLs to existing jcr resources. * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe And i tend to think a tiny wildcard in a path parameter would be nicer :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2726) allow simple wildcards in servlet paths
[ https://issues.apache.org/jira/browse/SLING-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier resolved SLING-2726. Resolution: Won't Fix see above allow simple wildcards in servlet paths --- Key: SLING-2726 URL: https://issues.apache.org/jira/browse/SLING-2726 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Nicolas Peltier Priority: Minor While i'm a big fan/evangelist of sling unique servlet management. I tend to think this would be nice to allow minimum wildcard for servlet paths, i.e. /a/b/* (no suffix), as some use cases can't be cover right now with jcr based resources + path servlets. Basically every resource model where you don't need a jcr node for (while it's very convenient most of the time). I'm thinking for example of having a profile servlet with a nice public /profile/jdoe.html url. Right now my possibilities are * to create a flat tree of fake user nodes under a profile node just for the sake of my urls (don't need righs handling, don't need other verbs for the same resource), * to have tons of vanityUrls (not meant for that kind of usage) * to create my own ResourceProvider that map that kind of URLs to existing jcr resources. * to switch to /profile.jdoe.html, or /profile.html?uid=jdoe And i tend to think a tiny wildcard in a path parameter would be nicer :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SLING-3368) Add toMap iterable to resp. JSONObject and JSONArray
Nicolas Peltier created SLING-3368: -- Summary: Add toMap iterable to resp. JSONObject and JSONArray Key: SLING-3368 URL: https://issues.apache.org/jira/browse/SLING-3368 Project: Sling Issue Type: Improvement Components: Commons Reporter: Nicolas Peltier Priority: Minor Map JSONObject.toMap and JSONArray implementing Iterable allows better usage of those classes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (SLING-3368) Add toMap iterable to resp. JSONObject and JSONArray
[ https://issues.apache.org/jira/browse/SLING-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-3368: --- Attachment: [json]_add_other_ways_to_use_JSONArray_and_JSONObject.patch proposed patch Add toMap iterable to resp. JSONObject and JSONArray -- Key: SLING-3368 URL: https://issues.apache.org/jira/browse/SLING-3368 Project: Sling Issue Type: Improvement Components: Commons Reporter: Nicolas Peltier Priority: Minor Attachments: [json]_add_other_ways_to_use_JSONArray_and_JSONObject.patch Map JSONObject.toMap and JSONArray implementing Iterable allows better usage of those classes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (SLING-3368) Add toMap iterable to resp. JSONObject and JSONArray
[ https://issues.apache.org/jira/browse/SLING-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890717#comment-13890717 ] Nicolas Peltier commented on SLING-3368: Hi, note that toMap is not called getMap :-), it's meant to be a conversion method. Implementation is a getter then, i agree. I've contributed this because i've been a lot of time aching to manipulate JSONObject JSONArray in a simple way. I agree this gives opportunities to mess up an object, but the API doesn't guarantee that, it can be strenghtened later on (or now if you think it's still worth it). Add toMap iterable to resp. JSONObject and JSONArray -- Key: SLING-3368 URL: https://issues.apache.org/jira/browse/SLING-3368 Project: Sling Issue Type: Improvement Components: Commons Reporter: Nicolas Peltier Priority: Minor Attachments: [json]_add_other_ways_to_use_JSONArray_and_JSONObject.patch Map JSONObject.toMap and JSONArray implementing Iterable allows better usage of those classes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (SLING-3368) Simplify JSONObject and JSONArray access
[ https://issues.apache.org/jira/browse/SLING-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-3368: --- Summary: Simplify JSONObject and JSONArray access (was: Add toMap iterable to resp. JSONObject and JSONArray) Simplify JSONObject and JSONArray access Key: SLING-3368 URL: https://issues.apache.org/jira/browse/SLING-3368 Project: Sling Issue Type: Improvement Components: Commons Reporter: Nicolas Peltier Priority: Minor Attachments: [json]_add_other_ways_to_use_JSONArray_and_JSONObject.patch Map JSONObject.toMap and JSONArray implementing Iterable allows better usage of those classes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (SLING-3368) Simplify JSONObject and JSONArray access
[ https://issues.apache.org/jira/browse/SLING-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890768#comment-13890768 ] Nicolas Peltier commented on SLING-3368: that's a nice idea :-) and would allow not to change the API. What others think? There is still the immutable debate: should this be adapted in immutable objects? Simplify JSONObject and JSONArray access Key: SLING-3368 URL: https://issues.apache.org/jira/browse/SLING-3368 Project: Sling Issue Type: Improvement Components: Commons Reporter: Nicolas Peltier Priority: Minor Attachments: [json]_add_other_ways_to_use_JSONArray_and_JSONObject.patch Map JSONObject.toMap and JSONArray implementing Iterable allows better usage of those classes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (SLING-3368) Simplify JSONObject and JSONArray access
[ https://issues.apache.org/jira/browse/SLING-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890794#comment-13890794 ] Nicolas Peltier commented on SLING-3368: right, will come back with a new patch soon then (unless somebody shouts :-) Simplify JSONObject and JSONArray access Key: SLING-3368 URL: https://issues.apache.org/jira/browse/SLING-3368 Project: Sling Issue Type: Improvement Components: Commons Reporter: Nicolas Peltier Priority: Minor Attachments: [json]_add_other_ways_to_use_JSONArray_and_JSONObject.patch Map JSONObject.toMap and JSONArray implementing Iterable allows better usage of those classes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (SLING-3368) Simplify JSONObject and JSONArray access
[ https://issues.apache.org/jira/browse/SLING-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-3368: --- Attachment: [json]_add_JSONArray_adaptTo(List_class),_JSONObject_adaptTo(Map_class),_iterable_JSONArra.patch proposed path for adaptTo: - kept Iterable for JSONArray for different use cases - makes immutable the returned values - added some basic tests Simplify JSONObject and JSONArray access Key: SLING-3368 URL: https://issues.apache.org/jira/browse/SLING-3368 Project: Sling Issue Type: Improvement Components: Commons Reporter: Nicolas Peltier Priority: Minor Attachments: [json]_add_JSONArray_adaptTo(List_class),_JSONObject_adaptTo(Map_class),_iterable_JSONArra.patch, [json]_add_other_ways_to_use_JSONArray_and_JSONObject.patch Map JSONObject.toMap and JSONArray implementing Iterable allows better usage of those classes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (SLING-3368) Simplify JSONObject and JSONArray access
[ https://issues.apache.org/jira/browse/SLING-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890908#comment-13890908 ] Nicolas Peltier edited comment on SLING-3368 at 2/5/14 9:27 AM: proposed new patch - both JSONArray JSONObject implement Adaptable - kept Iterable implementation for JSONArray for different use cases - makes immutable the returned values - added some basic tests was (Author: npeltier): proposed path for adaptTo: - kept Iterable for JSONArray for different use cases - makes immutable the returned values - added some basic tests Simplify JSONObject and JSONArray access Key: SLING-3368 URL: https://issues.apache.org/jira/browse/SLING-3368 Project: Sling Issue Type: Improvement Components: Commons Reporter: Nicolas Peltier Priority: Minor Attachments: [json]_add_JSONArray_adaptTo(List_class),_JSONObject_adaptTo(Map_class),_iterable_JSONArra.patch, [json]_add_other_ways_to_use_JSONArray_and_JSONObject.patch Map JSONObject.toMap and JSONArray implementing Iterable allows better usage of those classes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (SLING-4024) Allow the ResourceResolver Mock Factory to initialize a Resolver via JSON
[ https://issues.apache.org/jira/browse/SLING-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14166503#comment-14166503 ] Nicolas Peltier commented on SLING-4024: Beside the fact that you'd switch from an open source project to the other, for sake of apache sling love :-), you should donate it. We started using those projects and it totally rocks! Allow the ResourceResolver Mock Factory to initialize a Resolver via JSON - Key: SLING-4024 URL: https://issues.apache.org/jira/browse/SLING-4024 Project: Sling Issue Type: Improvement Components: Testing Affects Versions: Testing ResourceResolver Mock 0.3.0 Reporter: dan mcweeney Sling can easily produce JSON for a tree of resources. It would make things much easier to be able to initialize the Resource Resolvers produced from the MockResourceResolverFactory with this JSON. It will allow people to create test fixtures based off real data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4362) [jcr mocks] Resource type not correctly loaded when using jcr mock
Nicolas Peltier created SLING-4362:
--
Summary: [jcr mocks] Resource type not correctly loaded when using
jcr mock
Key: SLING-4362
URL: https://issues.apache.org/jira/browse/SLING-4362
Project: Sling
Issue Type: Bug
Components: Testing
Affects Versions: Testing JCR Mock 1.1.2
Reporter: Nicolas Peltier
when setting resource resolver type to
ResourceResolverType.JCR_MOCK
such loaded json
{Code}
{
jcr:primaryType:nt:unstructured,
thisIs:root,
foo:{
jcr:primaryType:nt:unstructured,
sling:resourceType: fooType,
thisIs: child
}
}
{Code}
to /content
gives /content/foo a resourceType == nt:unstructured instead of fooType
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4362) [jcr mocks] Resource type not correctly loaded when using jcr mock
[
https://issues.apache.org/jira/browse/SLING-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-4362:
---
Description:
when setting resource resolver type to
ResourceResolverType.JCR_MOCK
such loaded json
{Code}
{
jcr:primaryType:nt:unstructured,
thisIs:root,
foo:{
jcr:primaryType:nt:unstructured,
sling:resourceType: fooType,
thisIs: child
}
}
{Code}
to /content
gives /content/foo a resourceType == nt:unstructured instead of fooType,
other properties (here thisIs) are correctly loaded
was:
when setting resource resolver type to
ResourceResolverType.JCR_MOCK
such loaded json
{Code}
{
jcr:primaryType:nt:unstructured,
thisIs:root,
foo:{
jcr:primaryType:nt:unstructured,
sling:resourceType: fooType,
thisIs: child
}
}
{Code}
to /content
gives /content/foo a resourceType == nt:unstructured instead of fooType
[jcr mocks] Resource type not correctly loaded when using jcr mock
--
Key: SLING-4362
URL: https://issues.apache.org/jira/browse/SLING-4362
Project: Sling
Issue Type: Bug
Components: Testing
Affects Versions: Testing JCR Mock 1.1.2
Reporter: Nicolas Peltier
when setting resource resolver type to
ResourceResolverType.JCR_MOCK
such loaded json
{Code}
{
jcr:primaryType:nt:unstructured,
thisIs:root,
foo:{
jcr:primaryType:nt:unstructured,
sling:resourceType: fooType,
thisIs: child
}
}
{Code}
to /content
gives /content/foo a resourceType == nt:unstructured instead of fooType,
other properties (here thisIs) are correctly loaded
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4362) [jcr mocks] Resource type not correctly loaded when using jcr mock
[
https://issues.apache.org/jira/browse/SLING-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295235#comment-14295235
]
Nicolas Peltier commented on SLING-4362:
my guess here is content loader uses modifiable value map to create the
resource that actually set the resourceType, but returns a resource based on
the node (whose transient space is disconected from the modifiable value map's
transient space).
[jcr mocks] Resource type not correctly loaded when using jcr mock
--
Key: SLING-4362
URL: https://issues.apache.org/jira/browse/SLING-4362
Project: Sling
Issue Type: Bug
Components: Testing
Affects Versions: Testing JCR Mock 1.1.2
Reporter: Nicolas Peltier
when setting resource resolver type to
ResourceResolverType.JCR_MOCK
such loaded json
{Code}
{
jcr:primaryType:nt:unstructured,
sling:resourceType: fooType,
thisIs: child
}
{Code}
to /content
gives /content/foo a resourceType == nt:unstructured instead of fooType,
other properties (here thisIs) are correctly loaded
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4362) [jcr mocks] Resource type not correctly loaded when using jcr mock
[
https://issues.apache.org/jira/browse/SLING-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-4362:
---
Description:
when setting resource resolver type to
ResourceResolverType.JCR_MOCK
such loaded json
{Code}
{
jcr:primaryType:nt:unstructured,
sling:resourceType: fooType,
thisIs: child
}
{Code}
to /content
gives /content/foo a resourceType == nt:unstructured instead of fooType,
other properties (here thisIs) are correctly loaded
was:
when setting resource resolver type to
ResourceResolverType.JCR_MOCK
such loaded json
{Code}
{
jcr:primaryType:nt:unstructured,
thisIs:root,
foo:{
jcr:primaryType:nt:unstructured,
sling:resourceType: fooType,
thisIs: child
}
}
{Code}
to /content
gives /content/foo a resourceType == nt:unstructured instead of fooType,
other properties (here thisIs) are correctly loaded
[jcr mocks] Resource type not correctly loaded when using jcr mock
--
Key: SLING-4362
URL: https://issues.apache.org/jira/browse/SLING-4362
Project: Sling
Issue Type: Bug
Components: Testing
Affects Versions: Testing JCR Mock 1.1.2
Reporter: Nicolas Peltier
when setting resource resolver type to
ResourceResolverType.JCR_MOCK
such loaded json
{Code}
{
jcr:primaryType:nt:unstructured,
sling:resourceType: fooType,
thisIs: child
}
{Code}
to /content
gives /content/foo a resourceType == nt:unstructured instead of fooType,
other properties (here thisIs) are correctly loaded
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4286) obsolete resources resource cleanup tool
Nicolas Peltier created SLING-4286: -- Summary: obsolete resources resource cleanup tool Key: SLING-4286 URL: https://issues.apache.org/jira/browse/SLING-4286 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Nicolas Peltier Priority: Minor Hi, along a repository life, some JCR resources whose resource type don't exist anymore accumulate. Those are not all to remove (e.g. a resource type can be set without renderer), but some others are just obsolete resources that will almost silently exist. Most common example is resource meant to be rendered without renderer (removed AEM component e.g.), that will generate following ERROR message in the logs, but not break anything: 21.08.2013 07:41:50.367 ERROR [10.5.81.178 [1377096110089] GET /content/blah/mother/resource.html HTTP/1.0] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource Paragraph, path=/content/blah/mother/resource/jcr:content/par/title, type=obsolete/component/title, cssClass=default, column=0/0, diffInfo=[null], resource=[, type=obsolete/component/title, path=/content/blah/mother/resource/jcr:content/par/title, resource=[JcrNodeResource, type=obsolete/component/title, superType=null, path=/content/blah/mother/resource/jcr:content/par/title]] i've written a small tool to clean those up safely in there https://github.com/npeltier/org.apache.sling.typecleanup i'd be happy to contribute if useful. Please comment :-) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4913) Allow exclusion filters on vault package builder
[
https://issues.apache.org/jira/browse/SLING-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647362#comment-14647362
]
Nicolas Peltier commented on SLING-4913:
thx [~mpetria], i confirm you {Code}/home/users|-.*/.tokens{Code} does the
trick for aem users
Allow exclusion filters on vault package builder
Key: SLING-4913
URL: https://issues.apache.org/jira/browse/SLING-4913
Project: Sling
Issue Type: Improvement
Components: Distribution
Reporter: Marius Petria
Assignee: Marius Petria
Fix For: Content Distribution Core 0.1.6
Allow exclusion filters on vault package builder, for example to exclude all
.tokens nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14974008#comment-14974008 ] Nicolas Peltier commented on SLING-5134: Hi [~olli], i see vote is in good shape :-) are you taking care of bringing in the code? should i attach the file to the ticket? (there are some personnal informations in there), send it to you by mail? Nicolas > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Oliver Lietz > Attachments: sling-pipes.tar.gz > > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14974918#comment-14974918 ] Nicolas Peltier commented on SLING-5134: thx [~olli]! license agreement read, and icla filed! > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Oliver Lietz > Attachments: sling-pipes.tar.gz > > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-5269) Sling Pipes IP clearance
[ https://issues.apache.org/jira/browse/SLING-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996741#comment-14996741 ] Nicolas Peltier edited comment on SLING-5269 at 11/9/15 3:45 PM: - fyi [~bdelacretaz][~olli], software grant scan is sent at secret...@apache.org was (Author: npeltier): fyi [~bdelacretaz][~olli], software grant scan is sent > Sling Pipes IP clearance > > > Key: SLING-5269 > URL: https://issues.apache.org/jira/browse/SLING-5269 > Project: Sling > Issue Type: Task > Components: Extensions >Reporter: Oliver Lietz >Assignee: Oliver Lietz > > This issue tracks the IP clearance for the donation of Sling Pipes > (SLING-5134). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5269) Sling Pipes IP clearance
[ https://issues.apache.org/jira/browse/SLING-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996741#comment-14996741 ] Nicolas Peltier commented on SLING-5269: fyi [~bdelacretaz][~olli], software grant scan is sent > Sling Pipes IP clearance > > > Key: SLING-5269 > URL: https://issues.apache.org/jira/browse/SLING-5269 > Project: Sling > Issue Type: Task > Components: Extensions >Reporter: Oliver Lietz >Assignee: Oliver Lietz > > This issue tracks the IP clearance for the donation of Sling Pipes > (SLING-5134). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5269) Sling Pipes IP clearance
[ https://issues.apache.org/jira/browse/SLING-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998390#comment-14998390 ] Nicolas Peltier commented on SLING-5269: [~bdelacretaz] [~olli] received aknowledgment that the software grant is filed, do you need a fwd of the mail? > Sling Pipes IP clearance > > > Key: SLING-5269 > URL: https://issues.apache.org/jira/browse/SLING-5269 > Project: Sling > Issue Type: Task > Components: Extensions >Reporter: Oliver Lietz >Assignee: Oliver Lietz > > This issue tracks the IP clearance for the donation of Sling Pipes > (SLING-5134). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14987232#comment-14987232 ] Nicolas Peltier commented on SLING-5134: Hey [~olli], i might have misunderstood / misread something, but Craig Russel told me ICLA was filed (& i mentioned that in the ticket) one week ago. Is there anything else i should do? > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Oliver Lietz > Attachments: sling-pipes.tar.gz > > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14993344#comment-14993344 ] Nicolas Peltier edited comment on SLING-5134 at 11/6/15 8:30 AM: - [~clr] (cc [~olli]) sorry about that :-/ should i forward the aknowledgment to some list? (would be sling-dev, here) was (Author: npeltier): [~clr] (cc [~olli]) sorry about that :-/ should i forward the aknowledgment to some list? > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Oliver Lietz > Attachments: sling-pipes.tar.gz > > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14993344#comment-14993344 ] Nicolas Peltier commented on SLING-5134: [~clr] (cc [~olli]) sorry about that :-/ should i forward the aknowledgment to some list? > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Oliver Lietz > Attachments: sling-pipes.tar.gz > > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5134: --- Attachment: sling-pipes.tar.gz > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier > Attachments: sling-pipes.tar.gz > > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-5134) Donation of sling pipes
[
https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14953128#comment-14953128
]
Nicolas Peltier edited comment on SLING-5134 at 10/15/15 11:20 AM:
---
(edited) shasum gives {Code}68eee1fa87784ea841c80e88b344ec92deb0f848{Code}
was (Author: npeltier):
(edited) shasum gives {Code}4ec1ad6c725b2d0a78dfb1fe89cbc7dc89494654{Code}
> Donation of sling pipes
> ---
>
> Key: SLING-5134
> URL: https://issues.apache.org/jira/browse/SLING-5134
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>Reporter: Nicolas Peltier
> Attachments: sling-pipes.tar.gz
>
>
> This issue tracks the donation of sling pipes as announced in [0]. Code &
> documentation are there [1] https://github.com/npeltier/sling-pipes, two open
> issues for now are tracked there a well [2]
> [0] http://sling.markmail.org/thread/n6yr6upogruem7qp
> [1] http://github.com/npeltier/sling-pipes
> [2] https://github.com/npeltier/sling-pipes/issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5134: --- Attachment: (was: sling-pipes.tar.gz) > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier > Attachments: sling-pipes.tar.gz > > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-5134) Donation of sling pipes
[
https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14953128#comment-14953128
]
Nicolas Peltier edited comment on SLING-5134 at 10/14/15 7:25 PM:
--
(edited) shasum gives {Code}4ec1ad6c725b2d0a78dfb1fe89cbc7dc89494654{Code}
was (Author: npeltier):
shasum gives {Code}7b199133ed12e915fd7c51410d8f15ae86e08da4{Code}
> Donation of sling pipes
> ---
>
> Key: SLING-5134
> URL: https://issues.apache.org/jira/browse/SLING-5134
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>Reporter: Nicolas Peltier
> Attachments: sling-pipes.tar.gz
>
>
> This issue tracks the donation of sling pipes as announced in [0]. Code &
> documentation are there [1] https://github.com/npeltier/sling-pipes, two open
> issues for now are tracked there a well [2]
> [0] http://sling.markmail.org/thread/n6yr6upogruem7qp
> [1] http://github.com/npeltier/sling-pipes
> [2] https://github.com/npeltier/sling-pipes/issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5134: --- Attachment: (was: sling-pipes.tar.gz) > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5134: --- Attachment: sling-pipes.tar.gz > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier > Attachments: sling-pipes.tar.gz > > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-5134) Donation of sling pipes
[
https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14953128#comment-14953128
]
Nicolas Peltier edited comment on SLING-5134 at 10/17/15 8:49 AM:
--
fixed test issue {Code}fdf8052425fa6a66199f8fd5bec8bf6f420983b1{Code}
was (Author: npeltier):
(edited) shasum gives {Code}68eee1fa87784ea841c80e88b344ec92deb0f848{Code}
> Donation of sling pipes
> ---
>
> Key: SLING-5134
> URL: https://issues.apache.org/jira/browse/SLING-5134
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>Reporter: Nicolas Peltier
> Attachments: sling-pipes.tar.gz
>
>
> This issue tracks the donation of sling pipes as announced in [0]. Code &
> documentation are there [1] https://github.com/npeltier/sling-pipes, two open
> issues for now are tracked there a well [2]
> [0] http://sling.markmail.org/thread/n6yr6upogruem7qp
> [1] http://github.com/npeltier/sling-pipes
> [2] https://github.com/npeltier/sling-pipes/issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5134: --- Attachment: sling-pipes.tar.gz > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier > Attachments: sling-pipes.tar.gz > > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5134: --- Attachment: (was: sling-pipes.tar.gz) > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5134) Donation of sling pipes
Nicolas Peltier created SLING-5134: -- Summary: Donation of sling pipes Key: SLING-5134 URL: https://issues.apache.org/jira/browse/SLING-5134 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Nicolas Peltier This issue tracks the donation of sling pipes as announced in [0]. Code & documentation are there [1] https://github.com/npeltier/sling-pipes, two open issues for now are tracked there a well [2] [0] http://sling.markmail.org/thread/n6yr6upogruem7qp [1] http://github.com/npeltier/sling-pipes [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5134) Donation of sling pipes
[
https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-5134:
---
Attachment: sling-pipes.tar.gz
shasum gives {Code}7b199133ed12e915fd7c51410d8f15ae86e08da4{Code}
> Donation of sling pipes
> ---
>
> Key: SLING-5134
> URL: https://issues.apache.org/jira/browse/SLING-5134
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>Reporter: Nicolas Peltier
> Attachments: sling-pipes.tar.gz
>
>
> This issue tracks the donation of sling pipes as announced in [0]. Code &
> documentation are there [1] https://github.com/npeltier/sling-pipes, two open
> issues for now are tracked there a well [2]
> [0] http://sling.markmail.org/thread/n6yr6upogruem7qp
> [1] http://github.com/npeltier/sling-pipes
> [2] https://github.com/npeltier/sling-pipes/issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4862) Sling Health Checks Servlet
[ https://issues.apache.org/jira/browse/SLING-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14618537#comment-14618537 ] Nicolas Peltier commented on SLING-4862: on the wish list :-) it would be nice to have an osgi flag we can set to make the call fail in all cases (maintenance, ...) not sure if it is better to put it here, or create a dummy health check repeats what you tell him in its conf. Sling Health Checks Servlet --- Key: SLING-4862 URL: https://issues.apache.org/jira/browse/SLING-4862 Project: Sling Issue Type: Improvement Components: Health Check Reporter: Bertrand Delacretaz Priority: Minor A Servlet that can execute health checks would be useful. It can take as input the tags of the HCs to execute, and output their results in JSON format. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4862) Sling Health Checks Servlet
[ https://issues.apache.org/jira/browse/SLING-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14618564#comment-14618564 ] Nicolas Peltier commented on SLING-4862: [~bdelacretaz] that's it yes, + also configurable OK/NOK messages, and decoupling of the response rendering (txt, html, json might be needed in some cases) Sling Health Checks Servlet --- Key: SLING-4862 URL: https://issues.apache.org/jira/browse/SLING-4862 Project: Sling Issue Type: Improvement Components: Health Check Reporter: Bertrand Delacretaz Priority: Minor A Servlet that can execute health checks would be useful. It can take as input the tags of the HCs to execute, and output their results in JSON format. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4862) Sling Health Checks Servlet
[ https://issues.apache.org/jira/browse/SLING-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14718144#comment-14718144 ] Nicolas Peltier commented on SLING-4862: yep [~henzlerg], looks good, thanks! Sling Health Checks Servlet --- Key: SLING-4862 URL: https://issues.apache.org/jira/browse/SLING-4862 Project: Sling Issue Type: Improvement Components: Health Check Reporter: Bertrand Delacretaz Priority: Minor Fix For: Health Check Core 1.2.4 Attachments: SLING-4862-HealthCheckExecutorServlet-v2.patch, SLING-4862-HealthCheckExecutorServlet.patch A Servlet that can execute health checks would be useful. It can take as input the tags of the HCs to execute, and output their results in JSON format. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4971) static node name not allowed as a script ancestor
[
https://issues.apache.org/jira/browse/SLING-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-4971:
---
Summary: static node name not allowed as a script ancestor (was: static
node name not allowed as a script ancestor)
static node name not allowed as a script ancestor
---
Key: SLING-4971
URL: https://issues.apache.org/jira/browse/SLING-4971
Project: Sling
Issue Type: Bug
Components: Scripting
Affects Versions: Scripting Sightly Engine 1.0.2
Reporter: Nicolas Peltier
Priority: Minor
Looks like having static as a script ancestor (e.g.
/apps/blah/static/foo/foo.html) will break badly the script rendering (and
all the rendering process), yelling:
{noformat}
Line 1, column 0 : The declared package does not match the expected
package apps.blah.static.foo
Line 19, column 994 : Syntax error on token static, Identifier expected
at
org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileSource(SightlyJavaCompilerService.java:143)
at
org.apache.sling.scripting.sightly.impl.engine.UnitLoader.createUnit(UnitLoader.java:140)
at
org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.evaluateScript(SightlyScriptEngine.java:94)
at
org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.eval(SightlyScriptEngine.java:83)
at
org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:361)
at
org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:171)
at
org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:463)
... 258 common frames omitted
Caused by:
org.apache.sling.scripting.sightly.impl.compiler.CompilerException:
org.apache.sling.scripting.sightly.impl.compiler.CompilerException:
Compilation errors in apps/blah/static/foo/SightlyJava_foo.java:
Line 1, column 0 : The declared package does not match the expected
package apps.blah.static.foo
Line 19, column 994 : Syntax error on token static, Identifier expected
at
org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileJavaResource(SightlyJavaCompilerService.java:258)
at
org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileSource(SightlyJavaCompilerService.java:141)
... 264 common frames omitted
Caused by:
org.apache.sling.scripting.sightly.impl.compiler.CompilerException:
Compilation errors in apps/blah/static/foo/SightlyJava_foo.java:
Line 1, column 0 : The declared package does not match the expected
package apps.blah.static.foo
Line 19, column 994 : Syntax error on token static, Identifier expected
at
org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileJavaResource(SightlyJavaCompilerService.java:250)
... 265 common frames omitted
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4971) static node name not allowed as a script ancestor
Nicolas Peltier created SLING-4971:
--
Summary: static node name not allowed as a script ancestor
Key: SLING-4971
URL: https://issues.apache.org/jira/browse/SLING-4971
Project: Sling
Issue Type: Bug
Components: Scripting
Affects Versions: Scripting Sightly Engine 1.0.2
Reporter: Nicolas Peltier
Priority: Minor
Looks like having static as a script ancestor (e.g.
/apps/blah/static/foo/foo.html) will break badly the script rendering (and all
the rendering process), yelling:
{noformat}
Line 1, column 0 : The declared package does not match the expected package
apps.blah.static.foo
Line 19, column 994 : Syntax error on token static, Identifier expected
at
org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileSource(SightlyJavaCompilerService.java:143)
at
org.apache.sling.scripting.sightly.impl.engine.UnitLoader.createUnit(UnitLoader.java:140)
at
org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.evaluateScript(SightlyScriptEngine.java:94)
at
org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.eval(SightlyScriptEngine.java:83)
at
org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:361)
at
org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:171)
at
org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:463)
... 258 common frames omitted
Caused by: org.apache.sling.scripting.sightly.impl.compiler.CompilerException:
org.apache.sling.scripting.sightly.impl.compiler.CompilerException: Compilation
errors in apps/blah/static/foo/SightlyJava_foo.java:
Line 1, column 0 : The declared package does not match the expected package
apps.blah.static.foo
Line 19, column 994 : Syntax error on token static, Identifier expected
at
org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileJavaResource(SightlyJavaCompilerService.java:258)
at
org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileSource(SightlyJavaCompilerService.java:141)
... 264 common frames omitted
Caused by: org.apache.sling.scripting.sightly.impl.compiler.CompilerException:
Compilation errors in apps/blah/static/foo/SightlyJava_foo.java:
Line 1, column 0 : The declared package does not match the expected package
apps.blah.static.foo
Line 19, column 994 : Syntax error on token static, Identifier expected
at
org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileJavaResource(SightlyJavaCompilerService.java:250)
... 265 common frames omitted
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-5357) [ext][sling pipes] documentation
Nicolas Peltier created SLING-5357: -- Summary: [ext][sling pipes] documentation Key: SLING-5357 URL: https://issues.apache.org/jira/browse/SLING-5357 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Nicolas Peltier Priority: Minor Now SLING-5134, github documentation [0] should be migrated to Sling's site [0] https://github.com/npeltier/sling-pipes/blob/master/README.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5134) Donation of sling pipes
[ https://issues.apache.org/jira/browse/SLING-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045017#comment-15045017 ] Nicolas Peltier commented on SLING-5134: great [~bdelacretaz], thx! will know do a few JIRAs :-) > Donation of sling pipes > --- > > Key: SLING-5134 > URL: https://issues.apache.org/jira/browse/SLING-5134 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Bertrand Delacretaz > Attachments: sling-pipes.tar.gz > > > This issue tracks the donation of sling pipes as announced in [0]. Code & > documentation are there [1] https://github.com/npeltier/sling-pipes, two open > issues for now are tracked there a well [2] > [0] http://sling.markmail.org/thread/n6yr6upogruem7qp > [1] http://github.com/npeltier/sling-pipes > [2] https://github.com/npeltier/sling-pipes/issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5269) Sling Pipes IP clearance
[ https://issues.apache.org/jira/browse/SLING-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044631#comment-15044631 ] Nicolas Peltier commented on SLING-5269: Hi [~bdelacretaz], looks like [0] didn't bring much attention but falls into the lazy consensus rule? Nicolas [0] https://mail-archives.apache.org/mod_mbox/incubator-general/201512.mbox/browser > Sling Pipes IP clearance > > > Key: SLING-5269 > URL: https://issues.apache.org/jira/browse/SLING-5269 > Project: Sling > Issue Type: Task > Components: Extensions >Reporter: Oliver Lietz >Assignee: Bertrand Delacretaz > > This issue tracks the IP clearance for the donation of Sling Pipes > (SLING-5134). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5361) [ext][sling pipes] plain string expressions shouldn't be evaluated
Nicolas Peltier created SLING-5361: -- Summary: [ext][sling pipes] plain string expressions shouldn't be evaluated Key: SLING-5361 URL: https://issues.apache.org/jira/browse/SLING-5361 Project: Sling Issue Type: Bug Components: Extensions Reporter: Nicolas Peltier Priority: Minor when adding simple string expressions to a sling pipe, there are ERROR messages at execution mentionning the generated expression is not evaluated correctly. JS Engine shouldn't be called in the first place. This has been fixed between initial donation and effective commit (see [0]). will attach a patch with failing test & fix. [0] https://github.com/npeltier/sling-pipes/issues/10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5361) [ext][sling pipes] plain string expressions shouldn't be evaluated
[ https://issues.apache.org/jira/browse/SLING-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5361: --- Attachment: issue10.patch here is the patch, please review > [ext][sling pipes] plain string expressions shouldn't be evaluated > -- > > Key: SLING-5361 > URL: https://issues.apache.org/jira/browse/SLING-5361 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier >Priority: Minor > Attachments: issue10.patch > > > when adding simple string expressions to a sling pipe, there are ERROR > messages at execution mentionning the generated expression is not evaluated > correctly. JS Engine shouldn't be called in the first place. This has been > fixed between initial donation and effective commit (see [0]). > will attach a patch with failing test & fix. > [0] https://github.com/npeltier/sling-pipes/issues/10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5362) [ext][sling pipes] default output should be truncated
Nicolas Peltier created SLING-5362: -- Summary: [ext][sling pipes] default output should be truncated Key: SLING-5362 URL: https://issues.apache.org/jira/browse/SLING-5362 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Nicolas Peltier Priority: Minor default output is the paths of modified resources, which tends to be far too big as soon as you do lot of changes, should be truncated / paginated by default. This issue had been fixed already between initial donation and final commit. Will attach the patch to this ticket -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5362) [ext][sling pipes] default output should be truncated
[ https://issues.apache.org/jira/browse/SLING-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5362: --- Attachment: SLING-5362.patch patch corresponding to initial fix in https://github.com/npeltier/sling-pipes/issues/8 > [ext][sling pipes] default output should be truncated > - > > Key: SLING-5362 > URL: https://issues.apache.org/jira/browse/SLING-5362 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier >Priority: Minor > Attachments: SLING-5362.patch > > > default output is the paths of modified resources, which tends to be far too > big as soon as you do lot of changes, should be truncated / paginated by > default. > This issue had been fixed already between initial donation and final commit. > Will attach the patch to this ticket -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5357) [ext][sling pipes] documentation
[ https://issues.apache.org/jira/browse/SLING-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045958#comment-15045958 ] Nicolas Peltier commented on SLING-5357: thx [~rombert]! is there a quick way to test the changes i did locally? Tried /tools/build/build_site.pl, but after installed few dependencies, still have issues.. Guess there must be a more straight forward way? > [ext][sling pipes] documentation > > > Key: SLING-5357 > URL: https://issues.apache.org/jira/browse/SLING-5357 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier >Priority: Minor > > Now SLING-5134, github documentation [0] should be migrated to Sling's site > [0] https://github.com/npeltier/sling-pipes/blob/master/README.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5362) [ext][sling pipes] default output should be truncated
[ https://issues.apache.org/jira/browse/SLING-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5362: --- Priority: Major (was: Minor) > [ext][sling pipes] default output should be truncated > - > > Key: SLING-5362 > URL: https://issues.apache.org/jira/browse/SLING-5362 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5362.patch > > > default output is the paths of modified resources, which tends to be far too > big as soon as you do lot of changes, should be truncated / paginated by > default. > This issue had been fixed already between initial donation and final commit. > Will attach the patch to this ticket -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5362) [ext][sling pipes] default output should be truncated
[ https://issues.apache.org/jira/browse/SLING-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058053#comment-15058053 ] Nicolas Peltier commented on SLING-5362: setting to major as in the context of the tool it's important > [ext][sling pipes] default output should be truncated > - > > Key: SLING-5362 > URL: https://issues.apache.org/jira/browse/SLING-5362 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5362.patch > > > default output is the paths of modified resources, which tends to be far too > big as soon as you do lot of changes, should be truncated / paginated by > default. > This issue had been fixed already between initial donation and final commit. > Will attach the patch to this ticket -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5361) [ext][sling pipes] plain string expressions shouldn't be evaluated
[ https://issues.apache.org/jira/browse/SLING-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5361: --- Priority: Major (was: Minor) > [ext][sling pipes] plain string expressions shouldn't be evaluated > -- > > Key: SLING-5361 > URL: https://issues.apache.org/jira/browse/SLING-5361 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: issue10.patch > > > when adding simple string expressions to a sling pipe, there are ERROR > messages at execution mentionning the generated expression is not evaluated > correctly. JS Engine shouldn't be called in the first place. This has been > fixed between initial donation and effective commit (see [0]). > will attach a patch with failing test & fix. > [0] https://github.com/npeltier/sling-pipes/issues/10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5361) [ext][sling pipes] plain string expressions shouldn't be evaluated
[ https://issues.apache.org/jira/browse/SLING-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058052#comment-15058052 ] Nicolas Peltier commented on SLING-5361: setting to major so the issue is not filtered out :-), guess it's important in the context of the tool > [ext][sling pipes] plain string expressions shouldn't be evaluated > -- > > Key: SLING-5361 > URL: https://issues.apache.org/jira/browse/SLING-5361 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: issue10.patch > > > when adding simple string expressions to a sling pipe, there are ERROR > messages at execution mentionning the generated expression is not evaluated > correctly. JS Engine shouldn't be called in the first place. This has been > fixed between initial donation and effective commit (see [0]). > will attach a patch with failing test & fix. > [0] https://github.com/npeltier/sling-pipes/issues/10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5357) [ext][sling pipes] documentation
[ https://issues.apache.org/jira/browse/SLING-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5357: --- Attachment: SLING-5357.patch please find the documentation patch > [ext][sling pipes] documentation > > > Key: SLING-5357 > URL: https://issues.apache.org/jira/browse/SLING-5357 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier >Priority: Minor > Attachments: SLING-5357.patch > > > Now SLING-5134, github documentation [0] should be migrated to Sling's site > [0] https://github.com/npeltier/sling-pipes/blob/master/README.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-5357) [ext][sling pipes] documentation
[ https://issues.apache.org/jira/browse/SLING-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15054703#comment-15054703 ] Nicolas Peltier edited comment on SLING-5357 at 12/12/15 11:16 PM: --- please find the documentation patch (note that to be completely up to date, it should have SLING-5361 & SLING-5362 in) was (Author: npeltier): please find the documentation patch > [ext][sling pipes] documentation > > > Key: SLING-5357 > URL: https://issues.apache.org/jira/browse/SLING-5357 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier >Priority: Minor > Attachments: SLING-5357.patch > > > Now SLING-5134, github documentation [0] should be migrated to Sling's site > [0] https://github.com/npeltier/sling-pipes/blob/master/README.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5407) ui for sling pipes
Nicolas Peltier created SLING-5407:
--
Summary: ui for sling pipes
Key: SLING-5407
URL: https://issues.apache.org/jira/browse/SLING-5407
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Nicolas Peltier
a user interface would be nice :-) for now a tree explorer, or vault are needed
to create the configuration and make it a bit cumbersome to create / update
pipes.
An interface listing available pipes, allowing to quickly configure them,
validating also values, helping the user by showing which resources such & such
pipes output configured as this, would make this whole tool much better.
am thinking of a command line interface allowing such commands:
- rm /one/single/resource
- "find . -xpath "//element(*,nt:base)[@sling:resourceType='blah']" | rm"
- "find . -slingQuery "[@sling:resourceType='foo']" | write
{"sling:resourceType":"bar"}
plus "browsing" command:
- ls, cd, and cat
would be in the end (i think) better than web page
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5269) Sling Pipes IP clearance
[ https://issues.apache.org/jira/browse/SLING-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022047#comment-15022047 ] Nicolas Peltier commented on SLING-5269: bump :-) > Sling Pipes IP clearance > > > Key: SLING-5269 > URL: https://issues.apache.org/jira/browse/SLING-5269 > Project: Sling > Issue Type: Task > Components: Extensions >Reporter: Oliver Lietz >Assignee: Bertrand Delacretaz > > This issue tracks the IP clearance for the donation of Sling Pipes > (SLING-5134). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5758) Write Pipe should handle interpreting multi value properties
[ https://issues.apache.org/jira/browse/SLING-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312356#comment-15312356 ] Nicolas Peltier commented on SLING-5758: Hi [~jshurmer], just for sake of clarity, you would like multiple string properties to have each of their multiple string value compiled? > Write Pipe should handle interpreting multi value properties > > > Key: SLING-5758 > URL: https://issues.apache.org/jira/browse/SLING-5758 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Jordan Shurmer > > The Write pipe currently only interprets String values as JS template > strings. All other types are saved as is. > I would like to expand this to include String Arrays as well -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5682) special json array import for sling post servlet to post orderered structures
[
https://issues.apache.org/jira/browse/SLING-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343854#comment-15343854
]
Nicolas Peltier commented on SLING-5682:
thx for digging that ticket out of the deads, [~sseif...@pro-vision.de]!
[~bdelacretaz] problem is that OrderedJsonReader is essentially a JsonReader.
Changes brought to JsonReader were done so it can be extended (and overriden)
with minimum of code duplication, basically not touching the logic, just
cutting things differently, with different visibility.
The only other alternative i see is to increase code duplication, if you prefer.
> special json array import for sling post servlet to post orderered structures
> -
>
> Key: SLING-5682
> URL: https://issues.apache.org/jira/browse/SLING-5682
> Project: Sling
> Issue Type: Improvement
> Components: Engine
>Reporter: Nicolas Peltier
> Attachments: SLING-5682.patch
>
>
> it is not possible right now to post an ordered structure through json data
> [0]. this ticket is for implementing [~bdelacretaz] proposal to use JSON
> Arrays:
> {noformat}
> {
>"title": "The parent node",
>"SLING:ordered": [{
>"SLING:name": "first",
>"title": "This comes first"
>}, {
>"SLING:name": "second",
>"title": "This comes second"
>}]
> }
> {noformat}
> This needs to be triggered by selector or content-type switch so that
> the existing POST behavior is unchanged.
> I suppose having SLING:ordered should then also set the appropriate
> mixin on the parent node.
> [0] http://sling.markmail.org/thread/plov2u7kibscn7sx
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5682) special json array import for sling post servlet to post orderered structures
[
https://issues.apache.org/jira/browse/SLING-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343881#comment-15343881
]
Nicolas Peltier commented on SLING-5682:
thanks [~bdelacretaz], i'll do that!
> special json array import for sling post servlet to post orderered structures
> -
>
> Key: SLING-5682
> URL: https://issues.apache.org/jira/browse/SLING-5682
> Project: Sling
> Issue Type: Improvement
> Components: Engine
>Reporter: Nicolas Peltier
> Attachments: SLING-5682.patch
>
>
> it is not possible right now to post an ordered structure through json data
> [0]. this ticket is for implementing [~bdelacretaz] proposal to use JSON
> Arrays:
> {noformat}
> {
>"title": "The parent node",
>"SLING:ordered": [{
>"SLING:name": "first",
>"title": "This comes first"
>}, {
>"SLING:name": "second",
>"title": "This comes second"
>}]
> }
> {noformat}
> This needs to be triggered by selector or content-type switch so that
> the existing POST behavior is unchanged.
> I suppose having SLING:ordered should then also set the appropriate
> mixin on the parent node.
> [0] http://sling.markmail.org/thread/plov2u7kibscn7sx
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-5431) PipeBinding NPE when evaluating null expression
Nicolas Peltier created SLING-5431: -- Summary: PipeBinding NPE when evaluating null expression Key: SLING-5431 URL: https://issues.apache.org/jira/browse/SLING-5431 Project: Sling Issue Type: Bug Components: Extensions Reporter: Nicolas Peltier PipeBindings should be able to evaluate null expressions or objects, and return null as value, right now it spits out a NPE. please find test & fix in the attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5433: --- Attachment: SLING-5433.patch > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5431) PipeBinding NPE when evaluating null expression
[ https://issues.apache.org/jira/browse/SLING-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5431: --- Attachment: SLING-5431.patch > PipeBinding NPE when evaluating null expression > --- > > Key: SLING-5431 > URL: https://issues.apache.org/jira/browse/SLING-5431 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5431.patch > > > PipeBindings should be able to evaluate null expressions or objects, and > return null as value, right now it spits out a NPE. > please find test & fix in the attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5433) WritePipe should remove a property when value is evaluated as null
Nicolas Peltier created SLING-5433: -- Summary: WritePipe should remove a property when value is evaluated as null Key: SLING-5433 URL: https://issues.apache.org/jira/browse/SLING-5433 Project: Sling Issue Type: Bug Components: Extensions Reporter: Nicolas Peltier it's not documented (will do), but a value evaluated as null in a write pipe conf should remove the property. It doesn't work right now as the target resource used for removal is the wrong one. failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101885#comment-15101885 ] Nicolas Peltier commented on SLING-5433: thx [~rombert], can you (quickly check) SLING-5431, as now i guess pipes tests are broken :-/ > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Robert Munteanu > Fix For: Pipes 1.0.0 > > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101807#comment-15101807 ] Nicolas Peltier commented on SLING-5433: without SLING-5431, this patch will throw a NPE during test > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5433) WritePipe should remove a property when value is evaluated as null
[ https://issues.apache.org/jira/browse/SLING-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101940#comment-15101940 ] Nicolas Peltier commented on SLING-5433: thx [~rombert]! should have i done differently? > WritePipe should remove a property when value is evaluated as null > -- > > Key: SLING-5433 > URL: https://issues.apache.org/jira/browse/SLING-5433 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier >Assignee: Robert Munteanu > Fix For: Pipes 1.0.0 > > Attachments: SLING-5433.patch > > > it's not documented (will do), but a value evaluated as null in a write pipe > conf should remove the property. It doesn't work right now as the target > resource used for removal is the wrong one. > failing test & fix patch attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5434: --- Attachment: SLING-5434.patch > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5434: --- Attachment: SLING-5434-DOC.patch also specified the fact you can use null in write pipe in the doc in the doc patch attached > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434-DOC.patch, SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5434) WritePipe shoud remove properties at the very end
Nicolas Peltier created SLING-5434: -- Summary: WritePipe shoud remove properties at the very end Key: SLING-5434 URL: https://issues.apache.org/jira/browse/SLING-5434 Project: Sling Issue Type: Bug Components: Extensions Reporter: Nicolas Peltier in order to allow all expressions at current state to use the values of properties to be removed. test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5434: --- Attachment: (was: SLING-5434.patch) > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434-DOC.patch, SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5434: --- Attachment: SLING-5434.patch > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434-DOC.patch, SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103055#comment-15103055 ] Nicolas Peltier commented on SLING-5434: updated the patch with users-list feedback > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434-DOC.patch, SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5682) special json array import for sling post servlet to post orderered structures
[
https://issues.apache.org/jira/browse/SLING-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-5682:
---
Attachment: SLING-5682-before.patch
[~bdelacretaz] just attached a patch adding better coverage for
createPrincipal* methods. Only miss the error case (in case of bad json
structure).
i did a separate patch even if there is no direct relationship between the two
patches: it's just the caller code that has been moved to a separate method,
handleSecurity
> special json array import for sling post servlet to post orderered structures
> -
>
> Key: SLING-5682
> URL: https://issues.apache.org/jira/browse/SLING-5682
> Project: Sling
> Issue Type: Improvement
> Components: Engine
>Reporter: Nicolas Peltier
> Attachments: SLING-5682-before.patch, SLING-5682.patch
>
>
> it is not possible right now to post an ordered structure through json data
> [0]. this ticket is for implementing [~bdelacretaz] proposal to use JSON
> Arrays:
> {noformat}
> {
>"title": "The parent node",
>"SLING:ordered": [{
>"SLING:name": "first",
>"title": "This comes first"
>}, {
>"SLING:name": "second",
>"title": "This comes second"
>}]
> }
> {noformat}
> This needs to be triggered by selector or content-type switch so that
> the existing POST behavior is unchanged.
> I suppose having SLING:ordered should then also set the appropriate
> mixin on the parent node.
> [0] http://sling.markmail.org/thread/plov2u7kibscn7sx
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-5523) filter pipe should be able to filter out resources that *have* a configured child
Nicolas Peltier created SLING-5523: -- Summary: filter pipe should be able to filter out resources that *have* a configured child Key: SLING-5523 URL: https://issues.apache.org/jira/browse/SLING-5523 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Nicolas Peltier implementing that feature as is could be complicated. A simple way of doing it is to add a "not" flag that inverts the filter results (if filter passes and not, filter fails, if filter fails and not, filter succeeds, filter succeeds in other cases (exclusive or of filter and not flag)) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5523) filter pipe should be able to filter out resources that *have* a configured child
[ https://issues.apache.org/jira/browse/SLING-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5523: --- Attachment: SLING-5523.patch attached patch adds the not operator and tests > filter pipe should be able to filter out resources that *have* a configured > child > - > > Key: SLING-5523 > URL: https://issues.apache.org/jira/browse/SLING-5523 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5523.patch > > > implementing that feature as is could be complicated. A simple way of doing > it is to add a "not" flag that inverts the filter results (if filter passes > and not, filter fails, if filter fails and not, filter succeeds, filter > succeeds in other cases (exclusive or of filter and not flag)) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5523) filter pipe should be able to filter out resources that *have* a configured child
[ https://issues.apache.org/jira/browse/SLING-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5523: --- Attachment: SLING-5434-5523-DOC.patch documentation patch for 5523 (cautious: contains SLING-5434 changes as well), will send a mail to the list for that, if SLING-5434 causes issues, i'll do a patch with this change only > filter pipe should be able to filter out resources that *have* a configured > child > - > > Key: SLING-5523 > URL: https://issues.apache.org/jira/browse/SLING-5523 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434-5523-DOC.patch, SLING-5523.patch > > > implementing that feature as is could be complicated. A simple way of doing > it is to add a "not" flag that inverts the filter results (if filter passes > and not, filter fails, if filter fails and not, filter succeeds, filter > succeeds in other cases (exclusive or of filter and not flag)) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5434) WritePipe shoud remove properties at the very end
[ https://issues.apache.org/jira/browse/SLING-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5434: --- Description: in order to allow all expressions at current state to use the values of properties to be removed. test & fix in attached patch related to thread http://mail-archives.apache.org/mod_mbox/sling-users/201601.mbox/%3C2FBC4C5C-A110-40A2-A7CF-F2B11170DD8F%40adobe.com%3E was: in order to allow all expressions at current state to use the values of properties to be removed. test & fix in attached patch > WritePipe shoud remove properties at the very end > - > > Key: SLING-5434 > URL: https://issues.apache.org/jira/browse/SLING-5434 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5434-DOC.patch, SLING-5434.patch > > > in order to allow all expressions at current state to use the values of > properties to be removed. > test & fix in attached patch > related to thread > http://mail-archives.apache.org/mod_mbox/sling-users/201601.mbox/%3C2FBC4C5C-A110-40A2-A7CF-F2B11170DD8F%40adobe.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-5640) add import distribution events
[ https://issues.apache.org/jira/browse/SLING-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229842#comment-15229842 ] Nicolas Peltier edited comment on SLING-5640 at 4/7/16 7:36 AM: thx [~mpetria]! closing, even if just for the sake of knitpicking, i could just change that bug into a documentation bug ;-) was (Author: npeltier): thx [~mpetria]! closing, even if for knitpick, i could just change that bug into a documentation bug ;-) > add import distribution events > -- > > Key: SLING-5640 > URL: https://issues.apache.org/jira/browse/SLING-5640 > Project: Sling > Issue Type: Bug > Components: Distribution >Reporter: Nicolas Peltier > > in order to handle distribution import, it would be handy to have a > distribution topic to listen to, ideally with the list of paths changed, or > at least the filters. i guess this should be added to the package importers ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-5640) add import distribution events
[ https://issues.apache.org/jira/browse/SLING-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier resolved SLING-5640. Resolution: Not A Bug thx [~mpetria]! closing, even if for knitpick, i could just change that bug into a documentation bug ;-) > add import distribution events > -- > > Key: SLING-5640 > URL: https://issues.apache.org/jira/browse/SLING-5640 > Project: Sling > Issue Type: Bug > Components: Distribution >Reporter: Nicolas Peltier > > in order to handle distribution import, it would be handy to have a > distribution topic to listen to, ideally with the list of paths changed, or > at least the filters. i guess this should be added to the package importers ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5640) add import distribution events
Nicolas Peltier created SLING-5640: -- Summary: add import distribution events Key: SLING-5640 URL: https://issues.apache.org/jira/browse/SLING-5640 Project: Sling Issue Type: Bug Components: Distribution Reporter: Nicolas Peltier in order to handle distribution import, it would be handy to have a distribution topic to listen to, ideally with the list of paths changed, or at least the filters. i guess this should be added to the package importers ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5682) special json array import for sling post servlet to post orderered structures
[
https://issues.apache.org/jira/browse/SLING-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-5682:
---
Description:
it is not possible right now to post an ordered structure through json data
[0]. this ticket is for implementing [~bdelacretaz] proposal to use JSON Arrays:
{noformat}
{
"title": "The parent node",
"SLING:ordered": [{
"SLING:name": "first",
"title": "This comes first"
}, {
"SLING:name": "second",
"title": "This comes second"
}]
}
{noformat}
This needs to be triggered by selector or content-type switch so that
the existing POST behavior is unchanged.
I suppose having SLING:ordered should then also set the appropriate
mixin on the parent node.
[0] http://sling.markmail.org/thread/plov2u7kibscn7sx
was:
it is not possible right now to post an ordered structure through json data
[0]. this ticket is for implementing [~bdelacretaz] proposal to use JSON Arrays:
{
"title": "The parent node",
"SLING:ordered": [{
"SLING:name": "first",
"title": "This comes first"
}, {
"SLING:name": "second",
"title": "This comes second"
}]
}
This needs to be triggered by selector or content-type switch so that
the existing POST behavior is unchanged.
I suppose having SLING:ordered should then also set the appropriate
mixin on the parent node.
[0] http://sling.markmail.org/thread/plov2u7kibscn7sx
> special json array import for sling post servlet to post orderered structures
> -
>
> Key: SLING-5682
> URL: https://issues.apache.org/jira/browse/SLING-5682
> Project: Sling
> Issue Type: Improvement
> Components: Engine
>Reporter: Nicolas Peltier
>
> it is not possible right now to post an ordered structure through json data
> [0]. this ticket is for implementing [~bdelacretaz] proposal to use JSON
> Arrays:
> {noformat}
> {
>"title": "The parent node",
>"SLING:ordered": [{
>"SLING:name": "first",
>"title": "This comes first"
>}, {
>"SLING:name": "second",
>"title": "This comes second"
>}]
> }
> {noformat}
> This needs to be triggered by selector or content-type switch so that
> the existing POST behavior is unchanged.
> I suppose having SLING:ordered should then also set the appropriate
> mixin on the parent node.
> [0] http://sling.markmail.org/thread/plov2u7kibscn7sx
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-5682) special json array import for sling post servlet to post orderered structures
Nicolas Peltier created SLING-5682:
--
Summary: special json array import for sling post servlet to post
orderered structures
Key: SLING-5682
URL: https://issues.apache.org/jira/browse/SLING-5682
Project: Sling
Issue Type: Improvement
Components: Engine
Reporter: Nicolas Peltier
it is not possible right now to post an ordered structure through json data
[0]. this ticket is for implementing [~bdelacretaz] proposal to use JSON Arrays:
{
"title": "The parent node",
"SLING:ordered": [{
"SLING:name": "first",
"title": "This comes first"
}, {
"SLING:name": "second",
"title": "This comes second"
}]
}
This needs to be triggered by selector or content-type switch so that
the existing POST behavior is unchanged.
I suppose having SLING:ordered should then also set the appropriate
mixin on the parent node.
[0] http://sling.markmail.org/thread/plov2u7kibscn7sx
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-5682) special json array import for sling post servlet to post orderered structures
[
https://issues.apache.org/jira/browse/SLING-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-5682:
---
Attachment: SLING-5682.patch
Hi [~bdelacretaz], you'll find a patch for this
i created the "ordered-json" extension for that matter. Was forced to modify a
bit the JSON reader so OrderedJsonReader (and its tests) reuses most of it.
> special json array import for sling post servlet to post orderered structures
> -
>
> Key: SLING-5682
> URL: https://issues.apache.org/jira/browse/SLING-5682
> Project: Sling
> Issue Type: Improvement
> Components: Engine
>Reporter: Nicolas Peltier
> Attachments: SLING-5682.patch
>
>
> it is not possible right now to post an ordered structure through json data
> [0]. this ticket is for implementing [~bdelacretaz] proposal to use JSON
> Arrays:
> {noformat}
> {
>"title": "The parent node",
>"SLING:ordered": [{
>"SLING:name": "first",
>"title": "This comes first"
>}, {
>"SLING:name": "second",
>"title": "This comes second"
>}]
> }
> {noformat}
> This needs to be triggered by selector or content-type switch so that
> the existing POST behavior is unchanged.
> I suppose having SLING:ordered should then also set the appropriate
> mixin on the parent node.
> [0] http://sling.markmail.org/thread/plov2u7kibscn7sx
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-5728) enhance filterpipe logging
Nicolas Peltier created SLING-5728: -- Summary: enhance filterpipe logging Key: SLING-5728 URL: https://issues.apache.org/jira/browse/SLING-5728 Project: Sling Issue Type: Bug Components: Extensions Reporter: Nicolas Peltier Priority: Minor - when a filter pipe's expression fails to generate a boolean, it should output the expression instead of a ClassCast exception, - when a filter pipe filters out a resource, it should log this in DEBUG, not INFO -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5729) pipe expressions should allow regexp with {n} or {n,m}
[
https://issues.apache.org/jira/browse/SLING-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-5729:
---
Attachment: SLING-5729.patch
failing tests + fix (enhancement of the regexp used for extracting expressions)
in attached patch
> pipe expressions should allow regexp with {n} or {n,m}
> --
>
> Key: SLING-5729
> URL: https://issues.apache.org/jira/browse/SLING-5729
> Project: Sling
> Issue Type: Bug
>Reporter: Nicolas Peltier
>Priority: Minor
> Attachments: SLING-5729.patch
>
>
> expressions like
> {Code}
> ${(new Regexp('/foo/bar/./../.{8}').test(path)}"
> {Code}
> can't work right now because of the rather simple regexp for extracting them
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-5729) pipe expressions should allow regexp with {n} or {n,m}
Nicolas Peltier created SLING-5729:
--
Summary: pipe expressions should allow regexp with {n} or {n,m}
Key: SLING-5729
URL: https://issues.apache.org/jira/browse/SLING-5729
Project: Sling
Issue Type: Bug
Reporter: Nicolas Peltier
Priority: Minor
expressions like
{Code}
${(new Regexp('/foo/bar/./../.{8}').test(path)}"
{Code}
can't work right now because of the rather simple regexp for extracting them
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-5728) enhance filterpipe logging
[ https://issues.apache.org/jira/browse/SLING-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5728: --- Attachment: SLING-5728.patch fix in attached patch > enhance filterpipe logging > -- > > Key: SLING-5728 > URL: https://issues.apache.org/jira/browse/SLING-5728 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Nicolas Peltier >Priority: Minor > Attachments: SLING-5728.patch > > > - when a filter pipe's expression fails to generate a boolean, it should > output the expression instead of a ClassCast exception, > - when a filter pipe filters out a resource, it should log this in DEBUG, not > INFO -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5718) Pipes size parameter is ignored
[
https://issues.apache.org/jira/browse/SLING-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278525#comment-15278525
]
Nicolas Peltier commented on SLING-5718:
Hi [~jshurmer] looks good to me, just maybe the <0 checks seems overkill to me.
(i don't have commit rights by the way, so you'll have to wait for a commiter
to see this)
> Pipes size parameter is ignored
> ---
>
> Key: SLING-5718
> URL: https://issues.apache.org/jira/browse/SLING-5718
> Project: Sling
> Issue Type: Bug
> Components: Extensions
>Reporter: Jordan Shurmer
> Attachments: SLING-5718.patch
>
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> The "size" parameter which can be passed in when executing a Pipe is ignored.
> line 92 of PlumbServlet.Java gets it
> {code}int size = request.getParameter(PARAM_SIZE) != null ?
> Integer.parseInt(request.getParameter(PARAM_SIZE)) : NB_MAX;{code}
> but it is never used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-5818) make sling pipe writer a persistent configuration
[ https://issues.apache.org/jira/browse/SLING-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5818: --- Attachment: SLING-5818.patch attaching patch that brings in "OutputWriter" interface, - PlumberServlet systematically uses it for outputing pipe execution results, with default writer outputing size & paths, - CustomWriter can be defined by adding a "writer" subnode to the resource, properties being dubbed in the output (with instantiation of the values), - CustomJsonWriter is a variation of CustomWriter, that comes from a JSON Object passed as a request parameter > make sling pipe writer a persistent configuration > - > > Key: SLING-5818 > URL: https://issues.apache.org/jira/browse/SLING-5818 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier > Attachments: SLING-5818.patch > > > right now, the only way to configure the output of a pipe is to add a json as > parameter of the pipe request. Sometimes the output is as important/complex > as the pipe itself, and should be persisted. > This could be also the opportunity to rewrite how writer is managed in a far > from ideal if/else block. > servlet/plumber should *always* take a writer in account, and call it each > time, > default being path writer, writer should still be overridable through a > request parameter -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5869) htl doesn't escape '%' character in uri context
[
https://issues.apache.org/jira/browse/SLING-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-5869:
---
Description:
% char in an href will not be escaped by sightly. This will cause an issue in
case a space is immediately after it, e.g.
"?message=5% fat only" will be escaped like "5%%20fat%20only", and %%20 will
crash some servers' request processing, at least it crashes sling's with
something like:
{noformat}
org.apache.sling.engine.impl.parameters.ParameterSupport
getRequestParameterMapInternal: Error parsing request
java.lang.IllegalArgumentException: Bad escape sequence: %=l
at org.apache.sling.engine.impl.parameters.Util.parseNVPairString(Util.java:330)
at org.apache.sling.engine.impl.parameters.Util.parseQueryString(Util.java:215)
at
org.apache.sling.engine.impl.parameters.ParameterSupport.getRequestParameterMapInternal(ParameterSupport.java:247)
at
org.apache.sling.engine.impl.parameters.ParameterSupport.getParameter(ParameterSupport.java:
{noformat}
was:
% char in an href will not be escaped by sightly. This will cause an issue in
case a space is immediately after it, e.g.
"5% fat only" will be escaped like "5%%20fat%20only", and %%20 will crash some
servers' request processing, at least it crashes sling's with something like:
{noformat}
org.apache.sling.engine.impl.parameters.ParameterSupport
getRequestParameterMapInternal: Error parsing request
java.lang.IllegalArgumentException: Bad escape sequence: %=l
at org.apache.sling.engine.impl.parameters.Util.parseNVPairString(Util.java:330)
at org.apache.sling.engine.impl.parameters.Util.parseQueryString(Util.java:215)
at
org.apache.sling.engine.impl.parameters.ParameterSupport.getRequestParameterMapInternal(ParameterSupport.java:247)
at
org.apache.sling.engine.impl.parameters.ParameterSupport.getParameter(ParameterSupport.java:
{noformat}
> htl doesn't escape '%' character in uri context
> ---
>
> Key: SLING-5869
> URL: https://issues.apache.org/jira/browse/SLING-5869
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Reporter: Nicolas Peltier
>
> % char in an href will not be escaped by sightly. This will cause an issue in
> case a space is immediately after it, e.g.
> "?message=5% fat only" will be escaped like "5%%20fat%20only", and %%20 will
> crash some servers' request processing, at least it crashes sling's with
> something like:
> {noformat}
> org.apache.sling.engine.impl.parameters.ParameterSupport
> getRequestParameterMapInternal: Error parsing request
> java.lang.IllegalArgumentException: Bad escape sequence: %=l
> at
> org.apache.sling.engine.impl.parameters.Util.parseNVPairString(Util.java:330)
> at
> org.apache.sling.engine.impl.parameters.Util.parseQueryString(Util.java:215)
> at
> org.apache.sling.engine.impl.parameters.ParameterSupport.getRequestParameterMapInternal(ParameterSupport.java:247)
> at
> org.apache.sling.engine.impl.parameters.ParameterSupport.getParameter(ParameterSupport.java:
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-5869) htl doesn't escape '%' character in uri context
Nicolas Peltier created SLING-5869:
--
Summary: htl doesn't escape '%' character in uri context
Key: SLING-5869
URL: https://issues.apache.org/jira/browse/SLING-5869
Project: Sling
Issue Type: Bug
Components: Scripting
Reporter: Nicolas Peltier
% char in an href will not be escaped by sightly. This will cause an issue in
case a space is immediately after it, e.g.
"5% fat only" will be escaped like "5%%20fat%20only", and %%20 will crash some
servers' request processing, at least it crashes sling's with something like:
{noformat}
org.apache.sling.engine.impl.parameters.ParameterSupport
getRequestParameterMapInternal: Error parsing request
java.lang.IllegalArgumentException: Bad escape sequence: %=l
at org.apache.sling.engine.impl.parameters.Util.parseNVPairString(Util.java:330)
at org.apache.sling.engine.impl.parameters.Util.parseQueryString(Util.java:215)
at
org.apache.sling.engine.impl.parameters.ParameterSupport.getRequestParameterMapInternal(ParameterSupport.java:247)
at
org.apache.sling.engine.impl.parameters.ParameterSupport.getParameter(ParameterSupport.java:
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-5826) add a change layer for sling pipes that modify content
Nicolas Peltier created SLING-5826: -- Summary: add a change layer for sling pipes that modify content Key: SLING-5826 URL: https://issues.apache.org/jira/browse/SLING-5826 Project: Sling Issue Type: Improvement Reporter: Nicolas Peltier would be nice to have a layer like operations & modification for post servlet for pipes, which would allow: - logging of operations done in the response (now we just have resulting resources or representations of them, and logs), - basis for adding backup functionnality -- This message was sent by Atlassian JIRA (v6.3.4#6332)
