[SLING-892] Allow servlets to be registered with extensions for all request methods

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Servlets Resolver 2.0.8
• Fix Version/s: Servlets Resolver 2.1.0
• Component/s: Servlets
• Assignee: Felix Meschberger
• Reporter: Alexander Klimetschek
• Created: 18/Mar/09 13:31
• Updated: 02/May/13 02:29
• Resolved: 26/Sep/10 12:47

Description

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).

Issue Links

• is depended upon by: SLING-1069 Servlets registered with for resourceTypes = sling/servlet/default responds to all extensions
• is duplicated by: SLING-1173 Support selecting non-GET scripts as per the request extension