You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Ian Boston (JIRA)" <ji...@apache.org> on 2009/05/27 20:25:45 UTC
[jira] Created: (SLING-986) Dynamic URL rewriting as per discussion
on list.
Dynamic URL rewriting as per discussion on list.
------------------------------------------------
Key: SLING-986
URL: https://issues.apache.org/jira/browse/SLING-986
Project: Sling
Issue Type: New Feature
Components: Engine
Affects Versions: JCR Resource 2.0.6
Reporter: Ian Boston
Attachments: SLING-251.patch
After discussion on list http://markmail.org/thread/yvm3xoqtmpvrkijk
The patch to follow creates the ability to have nodes of the following form
/etc/map/http/myhost/~
-> sling:mapper=(prefix='~')
Where the value of the sling:mapper property is a valid OSGi Filter and locates a Service implementation of type MappingResolver.
Where the request path matches pattern, the service will be used to resolve the request path to an internal path and to map the internal path to a url.
The patch that follows is a first pass, that passes existing tests, but does not have unit test coverage.
One area of concern is the extent to which the bundle context needs to be propagated to facilitate a ServiceTracker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-986) Dynamic URL rewriting as per
discussion on list.
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston resolved SLING-986.
------------------------------
Resolution: Invalid
I now believe this approach to be invalid, as the same results can be achieved with a simple servlet request dispatch.
Closing as invalid to avoid adding more unused code to sling.
(We will have reverted this patch from our branch)
> Dynamic URL rewriting as per discussion on list.
> ------------------------------------------------
>
> Key: SLING-986
> URL: https://issues.apache.org/jira/browse/SLING-986
> Project: Sling
> Issue Type: New Feature
> Components: Engine
> Affects Versions: JCR Resource 2.0.6
> Reporter: Ian Boston
> Attachments: SLING-251.patch
>
>
> After discussion on list http://markmail.org/thread/yvm3xoqtmpvrkijk
> The patch to follow creates the ability to have nodes of the following form
> /etc/map/http/myhost/~
> -> sling:mapper=(prefix='~')
> Where the value of the sling:mapper property is a valid OSGi Filter and locates a Service implementation of type MappingResolver.
> Where the request path matches pattern, the service will be used to resolve the request path to an internal path and to map the internal path to a url.
> The patch that follows is a first pass, that passes existing tests, but does not have unit test coverage.
> One area of concern is the extent to which the bundle context needs to be propagated to facilitate a ServiceTracker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-986) Dynamic URL rewriting as per discussion
on list.
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston updated SLING-986:
-----------------------------
Attachment: SLING-251.patch
Patch (the patch name relates to the original but now closed issue)
> Dynamic URL rewriting as per discussion on list.
> ------------------------------------------------
>
> Key: SLING-986
> URL: https://issues.apache.org/jira/browse/SLING-986
> Project: Sling
> Issue Type: New Feature
> Components: Engine
> Affects Versions: JCR Resource 2.0.6
> Reporter: Ian Boston
> Attachments: SLING-251.patch
>
>
> After discussion on list http://markmail.org/thread/yvm3xoqtmpvrkijk
> The patch to follow creates the ability to have nodes of the following form
> /etc/map/http/myhost/~
> -> sling:mapper=(prefix='~')
> Where the value of the sling:mapper property is a valid OSGi Filter and locates a Service implementation of type MappingResolver.
> Where the request path matches pattern, the service will be used to resolve the request path to an internal path and to map the internal path to a url.
> The patch that follows is a first pass, that passes existing tests, but does not have unit test coverage.
> One area of concern is the extent to which the bundle context needs to be propagated to facilitate a ServiceTracker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-986) Dynamic URL rewriting as per
discussion on list.
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713736#action_12713736 ]
Felix Meschberger commented on SLING-986:
-----------------------------------------
Thanks for supplying this patch. I will look into it as soon as possible ...
> Dynamic URL rewriting as per discussion on list.
> ------------------------------------------------
>
> Key: SLING-986
> URL: https://issues.apache.org/jira/browse/SLING-986
> Project: Sling
> Issue Type: New Feature
> Components: Engine
> Affects Versions: JCR Resource 2.0.6
> Reporter: Ian Boston
> Attachments: SLING-251.patch
>
>
> After discussion on list http://markmail.org/thread/yvm3xoqtmpvrkijk
> The patch to follow creates the ability to have nodes of the following form
> /etc/map/http/myhost/~
> -> sling:mapper=(prefix='~')
> Where the value of the sling:mapper property is a valid OSGi Filter and locates a Service implementation of type MappingResolver.
> Where the request path matches pattern, the service will be used to resolve the request path to an internal path and to map the internal path to a url.
> The patch that follows is a first pass, that passes existing tests, but does not have unit test coverage.
> One area of concern is the extent to which the bundle context needs to be propagated to facilitate a ServiceTracker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.