[
https://issues.apache.org/jira/browse/SLING-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719976#comment-16719976
]
Julian Sedding commented on SLING-8170:
---------------------------------------
[~radu.cotescu] The proposal sounds reasonable, and I like that it brings
servlets and scripts on par in this respect.
Contrary to your proposal, for the reason of consistency, I suggest to call the
new registration property {{sling.servlet.resourceSuperTypes}} (i.e. plural).
All other registration properties (except "prefix") are already using plural
and allow multiple values. I assume that would require the implementation to
register the servlet for each combination of resource-type and
resource-super-type (+ selectors, extensions etc).
> 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)
