[jira] Reopened: (SLING-354) Better way to define the node name for a newly created node

[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reopened SLING-354: --- Assignee: (was: Carsten Ziegeler) Better way to define the node name for a

[jira] Commented: (SLING-354) Better way to define the node name for a newly created node

[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585915#action_12585915 ] Bertrand Delacretaz commented on SLING-354: --- I think the nameHint would be enough,

[jira] Commented: (SLING-192) JST script engine

[ https://issues.apache.org/jira/browse/SLING-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585946#action_12585946 ] Bertrand Delacretaz commented on SLING-192: --- Here's the test script, updated for

[jira] Commented: (SLING-354) Better way to define the node name for a newly created node

[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586007#action_12586007 ] Carsten Ziegeler commented on SLING-354: I agree that it makes sense to have a

[jira] Commented: (SLING-355) Empty Request Parameters should be handled as not present

[ https://issues.apache.org/jira/browse/SLING-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586008#action_12586008 ] Carsten Ziegeler commented on SLING-355: This is how it is currently implemented

Re: svn commit: r644750 - /incubator/sling/trunk/commons/json/src/main/java/org/apache/sling/commons/json/jcr/JsonItemWriter.java

Tobias Bocanegra wrote: why did you change this without a proper jira issue? i think that all clients that rely on this need to be informed. Yeah, my mistake - sorry! The changes fix some todos (the binary lengths is no correctly written to the response) and changing the prefix of the binary

Re: Checkin versionable nodes

Hi all, very interesting discussion and I see that this issues raises more possibilities and questions than I expected. I agree that the final checkin state of a node (or a set of nodes) is something that is application specific and therefore it should be possible for a bundle developer

[jira] Commented: (SLING-354) Better way to define the node name for a newly created node

[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586024#action_12586024 ] Bertrand Delacretaz commented on SLING-354: --- I'm not against having both, my idea

[jira] Commented: (SLING-354) Better way to define the node name for a newly created node

[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586026#action_12586026 ] Carsten Ziegeler commented on SLING-354: Ah ok, the current filtering of the other