You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/10/04 12:33:51 UTC
[jira] Created: (SLING-39) RequestDispatcher should use URLMapper
to try to resolve paths to Content objects
RequestDispatcher should use URLMapper 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 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-39) RequestDispatcher should use
ContentResolver to try to resolve paths to Content objects
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-39.
----------------------------------
Resolution: Fixed
Adapted various parts in Sling Core for this.
(1) The methods to access the resolved URL parts like Content, selectors, extension, suffix are moved from the RequestData to the ContentData. Now an included component has its own selectors, extension and suffix.
(2) The ComponentContextImpl class has been modified for support for the ContentResolver to feed a path provided to it to decompose the path, should it contain selectors, extension and suffix.
Please note, that there may still be some loose ends in this area:
* Parameters (?xxx&xx&xx..) are not yet supported by the Sling RequestDispatcher
* It should probably be decided what to do in case an included content has no selector, extension
and/or suffix. Should they just be empty (as in the default) or should the respective values from
the parent (including) component/content be inherited ?
> 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.
[jira] Updated: (SLING-39) RequestDispatcher should use
ContentResolver to try to resolve paths to Content objects
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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.