[
https://issues.apache.org/jira/browse/SLING-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Boston resolved SLING-1023.
-------------------------------
Resolution: Invalid
This is now invalid after the update to ResourceProviderEntry
Resolving.
> Allow NonExistant Resources to have a Resource Type
> ---------------------------------------------------
>
> Key: SLING-1023
> URL: https://issues.apache.org/jira/browse/SLING-1023
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.4
> Reporter: Ian Boston
> Attachments: SLING-1023.patch
>
>
> We have been using a patch to the jcr.resolver bundle that allows us to map
> non existent resources to a resource type so that they can be handled by a
> servlet registered to that resource type. Our use case is to allow a node to
> act as a marker and container for the virtual store where the URL path does
> not equal the JCR storage path.
> eg the URL
> /_user/messages/ieb/10000000001
> maps to
> /_user/messages/ed/fe/45/3e/ieb/23/ef/e4/d0/10000000001
> where only the node
> /_user/messages is marked with a resource type.
> Patch to follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
