You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/23 10:53:40 UTC

[jira] [Resolved] (SLING-1289) Additional ScriptSelectionTest case

     [ https://issues.apache.org/jira/browse/SLING-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-1289.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: Servlets Resolver 2.1.2

Thanks for your patch, Julian. It's applied in revision 1205348
                
> Additional ScriptSelectionTest case
> -----------------------------------
>
>                 Key: SLING-1289
>                 URL: https://issues.apache.org/jira/browse/SLING-1289
>             Project: Sling
>          Issue Type: Test
>          Components: Servlets
>    Affects Versions: Servlets Resolver 2.0.8
>            Reporter: Julian Sedding
>            Assignee: Carsten Ziegeler
>            Priority: Trivial
>             Fix For: Servlets Resolver 2.1.2
>
>         Attachments: SLING-1289-ScriptSelectionTest.patch
>
>
> The ScriptSelectionTest covers only one way to specify scripts for POST requests with a selector. Imagine resource /a with resource type foo/bar. A POST request to /a.print.html will be handled by the following two scripts:
> /apps/foo/bar/print/POST.esp
> /apps/foo/bar/print.POST.esp
> So far only the first case is tested. The attached patch adds a test for the second (IMHO more concise) syntax.
> I stumbled across this, because I was looking for documentation on the topic. There is a wiki page[1] with some (outdated?) information on the topic, but I couldn't find much more. Maybe I just missed it. If not, it would be nice to get this documented on the sling website, with the examples section extended to cover POST requests with selectors.
> [1] http://cwiki.apache.org/SLING/url-to-script-resolution.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira