[
https://issues.apache.org/jira/browse/SLING-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
santiago garcía pimentel updated SLING-4347:
Description:
Whenever a POST request is made and it contains a date string
hello oliver.
what's the status here? Will you move this project to Sling?
this is not decided yet, no precise plans yet. this depends if it is useful for
a broader audience in the sling community and projects/applications built with
sling. until then just try it out from wcm.io. additionally
[
https://issues.apache.org/jira/browse/SLING-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-3865.
---
Remove JcrResource.adaptTo(URL
--
Key: SLING-3865
[
https://issues.apache.org/jira/browse/SLING-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-4184.
---
Provide path mapping from JCR nodes to resource paths
[
https://issues.apache.org/jira/browse/SLING-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-3867.
---
Remove node/property adaptions
--
Key: SLING-3867
[
https://issues.apache.org/jira/browse/SLING-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-4116.
---
Content length check in JCRNodeResourceMetadata triggers
javax.jcr.ItemNotFoundException: No
[
https://issues.apache.org/jira/browse/SLING-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-4307.
---
Avoid caching JCR property values
-
Key:
santiago garcía pimentel created SLING-4347:
---
Summary: When a timezone is provided in a Date, it should be
stored as provided
Key: SLING-4347
URL: https://issues.apache.org/jira/browse/SLING-4347
[
https://issues.apache.org/jira/browse/SLING-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289514#comment-14289514
]
santiago garcía pimentel commented on SLING-4258:
-
I'm creating SLING-4347
The vote passed with three binding +1 votes
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
[
https://issues.apache.org/jira/browse/SLING-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289515#comment-14289515
]
santiago garcía pimentel commented on SLING-4347:
-
[~bdelacretaz] what do
See https://builds.apache.org/job/sling-trunk-1.6/2972/changes
See https://builds.apache.org/job/sling-trunk-1.7/1360/changes
[
https://issues.apache.org/jira/browse/SLING-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-4258.
Resolution: Fixed
I have now committed your contribution in
[
https://issues.apache.org/jira/browse/SLING-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-4212:
--
Attachment: resourcePath-API_noRequiredCheck.patch
attached is another updated version of the
See https://builds.apache.org/job/sling-trunk-1.8/652/changes
See https://builds.apache.org/job/sling-trunk-1.6/2973/changes
[
https://issues.apache.org/jira/browse/SLING-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-4212.
---
Resolution: Fixed
Completed: At revision: 1654430
patch applied
Sling Models: Allow
Hi,
we solved one critical issue
https://issues.apache.org/jira/browse/SLING-4343
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1177/
You can use this UNIX script to download the release and verify the
signatures:
See https://builds.apache.org/job/sling-trunk-1.8/653/changes
[
https://issues.apache.org/jira/browse/SLING-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289967#comment-14289967
]
santiago garcía pimentel commented on SLING-4212:
-
+1
Carsten
Am 23.01.15 um 13:20 schrieb Carsten Ziegeler:
Hi,
we solved one critical issue
https://issues.apache.org/jira/browse/SLING-4343
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1177/
You can use this UNIX script to download the release
On Fri, Jan 23, 2015 at 1:59 PM, Oliver Lietz apa...@oliverlietz.de wrote:
Whatever the approach is, if we want to allow multiple scripting engines
to
use the same extension we need to refactor the code from the
SlingScriptEngineManager.
Why? The ScriptEngine itself can decide if it
[
https://issues.apache.org/jira/browse/SLING-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Bailescu updated SLING-4346:
-
Attachment:
[
https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289243#comment-14289243
]
Tomek Rękawek edited comment on SLING-4318 at 1/23/15 1:39 PM:
[
https://issues.apache.org/jira/browse/SLING-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-4342.
--
Resolution: Fixed
Assignee: Felix Meschberger
Thanks for providing the patch. I
Hi
Am 23.01.2015 um 13:29 schrieb Radu Cotescu r...@apache.org:
On Fri, Jan 23, 2015 at 1:59 PM, Oliver Lietz apa...@oliverlietz.de wrote:
Whatever the approach is, if we want to allow multiple scripting engines
to
use the same extension we need to refactor the code from the
Hi
Am 23.01.2015 um 11:55 schrieb Oliver Lietz apa...@oliverlietz.de:
On Friday 23 January 2015 10:30:26 Felix Meschberger wrote:
Hi Radu
Thanks for starting this thread.
As I wrote in my other message [1], the ScriptEngine management is currently
laid out to have script engines to
[
https://issues.apache.org/jira/browse/SLING-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-4344.
Resolution: Fixed
Fix Version/s: i18n 2.3.4
Modifying i18n language node in a path
+1
Robert
On Thu, Jan 22, 2015 at 11:12 PM, Carsten Ziegeler cziege...@apache.org wrote:
Hi,
we solved one major deadlock issue
https://issues.apache.org/jira/browse/SLING/fixforversion/12329291
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1176/
Hello Robert,
On Thu, Jan 22, 2015 at 11:23 AM, Robert Munteanu romb...@apache.org
wrote:
Hi,
While doing a recent build of SlingQuery I realized that all packages
are exported with the project's version, so we need to add
package-info.java files and start versioning.
Thanks for pointing
See https://builds.apache.org/job/sling-trunk-1.6/2974/changes
[
https://issues.apache.org/jira/browse/SLING-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14288957#comment-14288957
]
Konrad Windszus commented on SLING-4344:
Applied a slightly modified patch in rev
+1
Robert
On Thu, Jan 22, 2015 at 11:10 PM, Stefan Seifert sseif...@pro-vision.de wrote:
Hi,
We solved 2 issues in JCR Mock 1.1.2:
https://issues.apache.org/jira/browse/SLING/fixforversion/12329091
We solved 2 issues in ResourceResolver Mock 1.1.2:
+1
On Jan 19, 2015, at 6:33 PM, Carsten Ziegeler cziege...@apache.org wrote:
Hi,
we solved some issues
https://issues.apache.org/jira/browse/SLING/fixforversion/12328895
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1174/
You can use this UNIX
On Fri, Jan 23, 2015 at 1:15 PM, Bertrand Delacretaz bdelacre...@apache.org
wrote:
Good point - we can consider that notation say anywhere in the first
200 chars of the script, so
?xml version=1.0 encoding=UTF-8?
!-- sling:language: thymeleaf --
foo/
would work, the pattern being
On Fri, Jan 23, 2015 at 1:59 PM, Oliver Lietz apa...@oliverlietz.de wrote:
Whatever the approach is, if we want to allow multiple scripting engines to
use the same extension we need to refactor the code from the
SlingScriptEngineManager.
Why? The ScriptEngine itself can decide if it kicks in
On Fri, Jan 23, 2015 at 2:08 PM, Robert Munteanu rob...@lmn.ro wrote:
If we configure various ScriptEngine implementations it becomes harder
to get an overview of what it configured where. It's even possible to
have conflicting patterns in two scripting engines.
We could have a master
On Friday 23 January 2015 13:33:37 Radu Cotescu wrote:
On Fri, Jan 23, 2015 at 1:15 PM, Bertrand Delacretaz bdelacre...@apache.org
wrote:
Good point - we can consider that notation say anywhere in the first
200 chars of the script, so
?xml version=1.0 encoding=UTF-8?
!--
Vlad Bailescu created SLING-4346:
Summary: Sightly: HtmlParser does not parse documents correctly
when comments span across internal char buffer size
Key: SLING-4346
URL:
Marius Petria created SLING-4348:
Summary: Sync agents do not process the queue anymore
Key: SLING-4348
URL: https://issues.apache.org/jira/browse/SLING-4348
Project: Sling
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SLING-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Petria updated SLING-4348:
-
Component/s: Distribution
Sync agents do not process the queue anymore
[
https://issues.apache.org/jira/browse/SLING-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14290484#comment-14290484
]
Marius Petria commented on SLING-4348:
--
Committed revision 1654477.
Sync agents do
[
https://issues.apache.org/jira/browse/SLING-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Petria resolved SLING-4348.
--
Resolution: Fixed
Sync agents do not process the queue anymore
[
https://issues.apache.org/jira/browse/SLING-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Petria reassigned SLING-4348:
Assignee: Marius Petria
Sync agents do not process the queue anymore
On Jan 22, 2015, at 6:50 PM, Oliver Lietz
apa...@oliverlietz.demailto:apa...@oliverlietz.de wrote:
On Thursday 22 January 2015 15:17:37 Antonio Sanso wrote:
On Jan 22, 2015, at 3:52 PM, Oliver Lietz
apa...@oliverlietz.demailto:apa...@oliverlietz.de wrote:
On Thursday 22 January 2015 13:02:05
[
https://issues.apache.org/jira/browse/SLING-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14288996#comment-14288996
]
Oliver Lietz commented on SLING-4330:
-
Threads collide .. lets continue the discussion on Radu’s thread [discussion]
allow Script Engines to also render components based on paths“
Regards
Felix
Am 23.01.2015 um 11:19 schrieb Felix Meschberger fmesc...@adobe.com:
Hi
So we have a problem in that two script engines are using the
On Fri, Jan 23, 2015 at 11:30 AM, Felix Meschberger fmesc...@adobe.com wrote:
We could extend our ScriptResolution as well like this. If the file begins
with a line of the form
#!engine-nameCRLF
Why not. It's a bit costly as you need to read part of the script
during resolution but I
On Fri, Jan 23, 2015 at 11:55 AM, Oliver Lietz apa...@oliverlietz.de wrote:
...Adding a Shebang to XML and HTML makes them invalid
Good point - we can consider that notation say anywhere in the first
200 chars of the script, so
?xml version=1.0 encoding=UTF-8?
!-- sling:language: thymeleaf
[
https://issues.apache.org/jira/browse/SLING-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289037#comment-14289037
]
Radu Cotescu commented on SLING-4330:
-
The {{ResourceResolution}} class is responsible
On Friday 23 January 2015 11:52:20 Bertrand Delacretaz wrote:
On Fri, Jan 23, 2015 at 11:30 AM, Felix Meschberger fmesc...@adobe.com
wrote:
We could extend our ScriptResolution as well like this. If the file begins
with a line of the form
#!engine-nameCRLF
Why not. It's a bit costly
Hi
So we have a problem in that two script engines are using the same
script/template extension ?
I think we cannot handle this with a mechanism such as SLING-4330. I also think
that script engines should not limit themselves in where they would like to be
evaluated. That’s none of their
Hi Radu
Thanks for starting this thread.
As I wrote in my other message [1], the ScriptEngine management is currently
laid out to have script engines to use disjoint extensions. Having two engines
with the same extension is not supported.
I also don’t really like to have multiple engines to
On Friday 23 January 2015 10:30:26 Felix Meschberger wrote:
Hi Radu
Thanks for starting this thread.
As I wrote in my other message [1], the ScriptEngine management is currently
laid out to have script engines to use disjoint extensions. Having two
engines with the same extension is not
On Fri, Jan 23, 2015 at 12:15 PM, Bertrand Delacretaz
bdelacre...@apache.org wrote:
... the pattern being sling:language followed by whitespace
and one word which is the language name
Or maybe sling:script to avoid confusion with human languages.
-Bertrand
GitHub user trekawek opened a pull request:
https://github.com/apache/sling/pull/58
SLING-4318 Servlet rendering a list of versions for the given resource.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/trekawek/sling
On Fri, Jan 23, 2015 at 1:03 AM, Mark Thomas ma...@apache.org wrote:
Sling developers,
The sling-trunk CI build managed to kill one of the buildbot slaves by
filling this directory with files until the file system ran out of inodes:
GitHub user trekawek opened a pull request:
https://github.com/apache/sling/pull/59
SLING-4318 :restore operation for the SlingPostServlet
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/trekawek/sling
[
https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289229#comment-14289229
]
ASF GitHub Bot commented on SLING-4318:
---
GitHub user trekawek opened a pull request:
[
https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289231#comment-14289231
]
ASF GitHub Bot commented on SLING-4318:
---
GitHub user trekawek opened a pull request:
[
https://issues.apache.org/jira/browse/SLING-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289232#comment-14289232
]
santiago garcía pimentel commented on SLING-4212:
-
[
https://issues.apache.org/jira/browse/SLING-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289234#comment-14289234
]
santiago garcía pimentel commented on SLING-4258:
-
[~bdelacretaz] do you
[
https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289243#comment-14289243
]
Tomek Rękawek commented on SLING-4318:
--
The {{;v=1.0}} parameter support has been
+1
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
+1
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
I share Felix's concern. If the ServletResolver's resolver is passed around,
please ensure it is a service user with minimal permissions required for
ServletResolver's needs.
We do *not* want to allow a resolver passed around from the ServletResolver to
be abused for accessing general
What about adding an additional property to the script resource?
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
Reminds me of the Mac Resource Forks … :-)
It would be neat to be able to set this in/on the script itself without having
to manage some out-of-band metadata.
Regards
Felix
Am 23.01.2015 um 15:15 schrieb Carsten Ziegeler cziege...@apache.org:
What about adding an additional property to the
Am 23.01.15 um 06:04 schrieb Felix Meschberger:
Adding a Shebang to XML and HTML makes them invalid. So that won't work.
Technically yes, but from a processing perspective no: because the
SlingScriptAdapterFactory will it it up and the ScriptEngine should not be
able to see it anymore.
[
https://issues.apache.org/jira/browse/SLING-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-4346.
--
Resolution: Fixed
Fix Version/s: (was: Scripting Sightly Engine 1.0.2)
Hi
Am 23.01.2015 um 15:11 schrieb Rob Ryan rr...@adobe.com:
I share Felix's concern. If the ServletResolver's resolver is passed around,
please ensure it is a service user with minimal permissions required for
ServletResolver's needs.
That’s a good point: This resource resolver should
FWIW, I think it would be more natural to set this on the container
node, so if you have /apps/foo/bar/something.html, I'd set
/apps/foo/bar@sling:script = html:thymeleaf.
We could, however, support both per-script and per-container settings,
but I don't think it is necessary to go more than one
On Fri, Jan 23, 2015 at 7:45 PM, Carsten Ziegeler cziege...@apache.org wrote:
What about adding an additional property to the script resource?
+1. This looks more safer and less disrupting as reading the property
is cheaper.
The script header approach looks nice but would require changes at
On Fri, Jan 23, 2015 at 4:21 PM, Chetan Mehrotra chetan.mehro...@gmail.com
wrote:
+1. This looks more safer and less disrupting as reading the property
is cheaper.
But we'd need a mixin, as scripts are usually nt:file nodes. Right?
[
https://issues.apache.org/jira/browse/SLING-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289353#comment-14289353
]
Justin Edelson commented on SLING-4337:
---
Proposed patch:
On Fri, Jan 23, 2015 at 3:41 PM, Chetan Mehrotra
chetan.mehro...@gmail.com wrote:
On Fri, Jan 23, 2015 at 7:59 PM, Radu Cotescu r...@apache.org wrote:
But we'd need a mixin, as scripts are usually nt:file nodes. Right?
...Other way would be to leverage the
jcr:mimeType on the child jcr:content
[
https://issues.apache.org/jira/browse/SLING-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289328#comment-14289328
]
Bertrand Delacretaz commented on SLING-4258:
I should be able to apply the
Hi,
On Fri, Jan 23, 2015 at 2:23 PM, Robert Munteanu romb...@apache.org wrote:
...I'm wondering if we still need the buildbot setup as the Jenkins
builds seem to be (mostly) stable these days
Right, I agree that we could remove the buildbot setup for now.
-Bertrand
Hi,
Isn't it possible to have some form of configuration that allows to
register scripting languages based on paths when needed?
E.g. by default we could following config:
*.jsp = JSP engine
*.html = Thymeleaf engine
And then by path we could override:
*.html in /foo = Sightly engine
It would
[
https://issues.apache.org/jira/browse/SLING-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned SLING-3440:
--
Assignee: Konrad Windszus
Clarify script resolution documentation with regard to
[
https://issues.apache.org/jira/browse/SLING-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289334#comment-14289334
]
Carsten Ziegeler commented on SLING-4340:
-
I think we should come to a conclusion
Hi Mark,
On Fri, Jan 23, 2015 at 12:03 AM, Mark Thomas ma...@apache.org wrote:
...However, please could you take a look at the
buildbot configuration for this build and figure out a) why this
happened and b) how to stop it happening again
For now, feel free to disable those jobs while we
[
https://issues.apache.org/jira/browse/SLING-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289452#comment-14289452
]
Konrad Windszus commented on SLING-3440:
I extended the documentation in r1654253.
Hi Rob,
The RuntimeExtensions are meant to process the outcome of a Sightly
expression. If such an extension would need to perform some processing
based on component resolution it's fair to pass it the same resolver that
the ServletResolver used.
I'll document in the RenderContext that this
On Fri, Jan 23, 2015 at 4:41 PM, Chetan Mehrotra chetan.mehro...@gmail.com
wrote:
Other way would be to leverage the
jcr:mimeType on the child jcr:content node which are mostly of type
nt:resource.
text/thymeleaf, text/sightly, text/jsp...? :)
[
https://issues.apache.org/jira/browse/SLING-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14287633#comment-14287633
]
Radu Cotescu edited comment on SLING-4342 at 1/23/15 12:40 PM:
[
https://issues.apache.org/jira/browse/SLING-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-3440.
Resolution: Fixed
Clarify script resolution documentation with regard to selectors
88 matches
Mail list logo
