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/05/29 16:38:45 UTC

[jira] Resolved: (SLING-489) Allow to register a Servlet for a ResourceType and a Path

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

Felix Meschberger resolved SLING-489.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

Modified servlet registration such that all possible path are registered in Rev. 661339.

Please close this issue if this works for you. Thanks.

> Allow to register a Servlet for a ResourceType and a Path
> ---------------------------------------------------------
>
>                 Key: SLING-489
>                 URL: https://issues.apache.org/jira/browse/SLING-489
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets Resolver
>    Affects Versions: 2.0.0
>            Reporter: christian
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> I have the following use case:
> I'd like to register a Servlet to handle the modification of a given ResourceType
> And in order to have a fallback I'd like to register the same servlet at a fixed path.
> Such a fallback case could be that the first Resource of the given Type has to be created.
> The declaration of this use case would look like this
> sling.servlet.paths = ["/my/fallback/path"]
> sling.servlet.resourcetypes = ["my.example.ResourceType"]
> On servlet resolution only the paths property is respected and any other property is ignored.
> I would suggest to change resolution such that a combination of paths, resourcetype and method is evaluated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.