[
https://issues.apache.org/jira/browse/SLING-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721023#comment-16721023
]
Konrad Windszus commented on SLING-8170:
----------------------------------------
[~radu.cotescu] Can you also come up with an IT for the servlet annotation at
https://github.com/apache/sling-org-apache-sling-servlets-annotations-it?
Hopefully it should be pretty straightforward. You only need to make sure that
you deploy the latest servlet resolver. Currently the ITs are based on Sling 9
(https://github.com/apache/sling-org-apache-sling-servlets-annotations-it/blob/5ec1de3a651b968c148f76ea4e92d417c28b0630/pom.xml#L88).
> Allow Sling servlets to declare a resource super type
> -----------------------------------------------------
>
> Key: SLING-8170
> URL: https://issues.apache.org/jira/browse/SLING-8170
> Project: Sling
> Issue Type: Improvement
> Components: API, Servlets
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Servlets Resolver 2.5.0, API 2.20.0, Sling Servlet
> Annotations 1.2.2
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In Sling scripts and servlets are equal [0]. However, currently a servlet
> cannot declare a resource super type property, in order to allow delegation /
> overlaying at runtime to another servlet, similar to how component scripts
> can do it through the {{sling:resourceSuperType}} optional property.
> Adding support for another registration property -
> {{sling.servlet.resourceSuperType}} - that accepts a String as value would
> allow to introduce a backwards compatible overlaying and inheritance
> capability. This property should only be considered for the registration
> together with the {{sling.servlet.resourceTypes}}.
> [0] -
> https://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html#fundamental-scripts-and-servlets-are-equal
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
