[
https://issues.apache.org/jira/browse/SLING-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-892.
-------------------------------------
Assignee: Felix Meschberger
Resolution: Fixed
Fixed in Rev. 1001418.
Modified ResourceCollector to allow the similar script names as for GET
requests with the difference, that the request method must be part of the name.
> Allow servlets to be registered with extensions for all request methods
> -----------------------------------------------------------------------
>
> Key: SLING-892
> URL: https://issues.apache.org/jira/browse/SLING-892
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Affects Versions: Servlets Resolver 2.0.8
> Reporter: Alexander Klimetschek
> Assignee: Felix Meschberger
> Fix For: Servlets Resolver 2.1.0
>
> Attachments: SLING-892.patch
>
>
> As SLING-754 introduced/fixed registering servlets for non-GET methods with
> selectors (eg. /apps/myapp/selector.POST.servlet), the same should be
> possible for extensions: /apps/myapp/extension.POST.servlet
> Use case: symmetric URLs when you import and export stuff at a given resource
> path:
> Export = GET @ /some/path/foo.ext
> Import/Update = POST @ /some/path/foo.ext
> Currently you are forced to either use a selector for the POST case
> (/some/path/foo.ext.ext) or to have a sling resource type set on the
> /some/path/foo, but then you could only have a single POST servlet for that
> resource type, regardless of the extension (which is unpractical if you for
> example have a resource type like "calendar", but want to import various
> calendar formats, separated by their file extension).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
