[
https://issues.apache.org/jira/browse/SLING-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574410#action_12574410
]
Bertrand Delacretaz commented on SLING-280:
-------------------------------------------
Modified patch applied in rev 633023.
I had to manually fix the patch as SLING-295 was committed already, please
cross-check that I didn't overlook something.
> ujax post serlvet should be able to insert new nodes at specified location
> --------------------------------------------------------------------------
>
> Key: SLING-280
> URL: https://issues.apache.org/jira/browse/SLING-280
> Project: Sling
> Issue Type: Improvement
> Reporter: Tobias Bocanegra
> Assignee: Bertrand Delacretaz
> Attachments: ujax_order_fix.r632454.patch
>
>
> the current version only supports: ujax:order = 0, which orders a newly
> created node above it's siblings.
> suggest to implement the following variants:
> ujax:order= ("below" | "above" ) [name]
> example:
> /a
> /b
> /c
> ujax:order="above b" -> /a, /newnode, /b, /c
> ujax:order="above a" -> /newnode, /a, /b, /c
> ujax:order="above" -> /newnode, /a, /b, /c
> ujax:order="below b" -> /a,/b,/newnode,/c
> ujax:order="below c" -> /a,/b,/c,/newnode
> ujax:order="below" -> /a,/b,/c,/newnode
> Please note that JCR does not support the 'below' ordering and it's 'above'
> handling is different. but i think in scripting environment, where you loop
> over a list. the "below" makes sense, since you don't need to know the next
> list item when drawing the 'insert' form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
