[
https://issues.apache.org/jira/browse/SLING-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888207#action_12888207
]
Carsten Ziegeler commented on SLING-1595:
-----------------------------------------
I'm not sure about this - I have at least three issues/questions with it:
- the jcr property map allows to specify a path to property to get a prop of a
child node like "foo/barprop". *If* we would support jcr:path we, should we
also support jcr:path for child nodes like foo/jcr:path (ok, getting jcr:path
and appending /foo would get me the path as well)?
- A lot of code I know relies on iterating over the props - with a new prop
jcr:path this would be returned in the iterator as well which might create
problems.
- This is a special jcr prop which is not available for other value map
implementations - so maybe we need something more generic?
> Add a jcr:path property to JcrPropertyMap
> -----------------------------------------
>
> Key: SLING-1595
> URL: https://issues.apache.org/jira/browse/SLING-1595
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Justin Edelson
> Fix For: JCR Resource 2.0.8
>
>
> Although it can be computed, it would be nice to always have access to a
> jcr:path property via the ValueMap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
