[
https://issues.apache.org/jira/browse/SLING-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573814#action_12573814
]
Felix Meschberger commented on SLING-262:
-----------------------------------------
Extend the ResourceProvider API in Rev. 632373 to state the handling of deeply
nested resources for which no actual parent hierarchy exists.
Consider for example a provided resource at /sample/path where the /sample
resource does not actually exist. To be able to traverse the resource tree to
the /sample/path resource, the resource provider's listChildren method is also
called for the "/" resource. In this case the method must return an iterator
providing a "/sample" resource. This resource should be a SyntheticResource
whose resource type MUST be set to ResourceProvider.RESOURCE_TYPE_SYNTHETIC
("sling:syntheticResourceProviderResource").
> ResourceProvider can not provide children list
> ----------------------------------------------
>
> Key: SLING-262
> URL: https://issues.apache.org/jira/browse/SLING-262
> Project: Sling
> Issue Type: Bug
> Components: Resource
> Reporter: christian
> Assignee: Felix Meschberger
>
> But the JcrResourceResolver's listChildren(Resource) relies on the Resource
> beeing descendable in order to list its children.
> See Ln 191 resp. 197 of JcrResourceProvider.
> Resources provided by a ResourceProvider can not implement Descendabel
> interface.
> This interface is not exported from the jcr/resource -bundle.
> As a Resoult its children never can be listed via the Resolver
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
