You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2009/03/18 14:31:53 UTC

[jira] Created: (SLING-892) Allow servlets to be registered with extensions for all request methods

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 Resolver
            Reporter: Alexander Klimetschek


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.