[
https://issues.apache.org/jira/browse/SLING-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-39:
-----------------------------------
Description:
Currently the Sling RequestDispatcher just tries to use the exact path to
resolve a Content object. Instead the ContentResolver should be used to enable
supplying selectors and extensions to the included request.
In addition supplying such information is not currently implemented in the
request inclusion functionality. This must also be implemented. As well support
must be added to the sling:include tag when used with the content attribute.
was:
Currently the Sling RequestDispatcher just tries to use the exact path to
resolve a Content object. Instead the URLMapper should be used to enable
supplying selectors and extensions to the included request.
In addition supplying such information is not currently implemented in the
request inclusion functionality. This must also be implemented. As well support
must be added to the sling:include tag when used with the content attribute.
Summary: RequestDispatcher should use ContentResolver to try to resolve
paths to Content objects (was: RequestDispatcher should use URLMapper to try
to resolve paths to Content objects)
Rename URLMapper to ContentResolver as per SLING-40
> RequestDispatcher should use ContentResolver to try to resolve paths to
> Content objects
> ---------------------------------------------------------------------------------------
>
> Key: SLING-39
> URL: https://issues.apache.org/jira/browse/SLING-39
> Project: Sling
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently the Sling RequestDispatcher just tries to use the exact path to
> resolve a Content object. Instead the ContentResolver should be used to
> enable supplying selectors and extensions to the included request.
> In addition supplying such information is not currently implemented in the
> request inclusion functionality. This must also be implemented. As well
> support must be added to the sling:include tag when used with the content
> attribute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.