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 2008/08/10 21:43:44 UTC
[jira] Created: (SLING-605) Extend RequestDispatcherOptions support
for requests without extension
Extend RequestDispatcherOptions support for requests without extension
----------------------------------------------------------------------
Key: SLING-605
URL: https://issues.apache.org/jira/browse/SLING-605
Project: Sling
Issue Type: Improvement
Components: Engine
Reporter: Felix Meschberger
Consider a request without a request extension -- e.g. http://host/some/content.pdf where the exact resource /some/content.pdf is being handled. When handling such requests and including other content the RequestDispatchOptions actually do not work because those are explicitly ignored in case the request extension is null.
The reason for this is, that (1) it is not possible to replace the request extension on included requests and (2) selectors are only possible if there is an extension.
The current implementation should be enhanced to set the request extension for inclusions should the current request extension be null.
Alternatively we might completely loosen the restriction placed on extensions (see (1) above) and allow to replace the request extension just like it is possible to replace the selectors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-605) Extend RequestDispatcherOptions support
for requests without extension
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-605.
-----------------------------------
Resolution: Won't Fix
Assignee: Felix Meschberger
This needs nothing to change. Because you can easily add extensions and replace selectors also by changing the inclusion path.
So consider you are handling request "/sample/file.pdf" with resource "/sample/file.pdf". To include handling for a selector, say "print.a4", you may do:
<sling:include path="${resource.path}.print.a4.pdf" />
This will resolve the string "/sample/file.pdf.print.a4.pdf" (albeit looking a bit strange) into the resource /sample/file.pdf, with selectors [ "print", "a4"] and extension "pdf".
> Extend RequestDispatcherOptions support for requests without extension
> ----------------------------------------------------------------------
>
> Key: SLING-605
> URL: https://issues.apache.org/jira/browse/SLING-605
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Consider a request without a request extension -- e.g. http://host/some/content.pdf where the exact resource /some/content.pdf is being handled. When handling such requests and including other content the RequestDispatchOptions actually do not work because those are explicitly ignored in case the request extension is null.
> The reason for this is, that (1) it is not possible to replace the request extension on included requests and (2) selectors are only possible if there is an extension.
> The current implementation should be enhanced to set the request extension for inclusions should the current request extension be null.
> Alternatively we might completely loosen the restriction placed on extensions (see (1) above) and allow to replace the request extension just like it is possible to replace the selectors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.