[
https://issues.apache.org/jira/browse/SLING-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720074#comment-16720074
]
Radu Cotescu commented on SLING-8170:
-------------------------------------
[~jsedding], thanks for reviewing the proposal! The new property should though
have a singular form. A resource can have only one resource super type, hence
why both the property name and the actual retrieved value from the Service
Reference are treated this way.
I'll go on with merging the two PRs and starting the releases.
> 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
>
> Time Spent: 20m
> 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)
