[
https://issues.apache.org/jira/browse/SLING-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888383#action_12888383
]
Alexander Klimetschek commented on SLING-1595:
----------------------------------------------
> The problem I'm running in to is that the JSON representation of a resource
> doesn't have the path in it.
Ok, but they have the path of the original requested object, at least for a
default json get request.
I had a similar case when building a servlet that returned json objects for a
query result - where each item can have a different path. But I just re-used
the JsonItemWriter in that case: I added the path myself and had the
JsonItemWriter do the rest (had to override a method, though).
But I think in any case this generally is an issue of the json representation,
not the ValueMap semantics. So a solution should enhance whatever creates the
JSON output, but not the ValueMap directly.
> 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.
