[
https://issues.apache.org/jira/browse/SLING-9055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058094#comment-17058094
]
Konrad Windszus commented on SLING-9055:
----------------------------------------
[~bdelacretaz] Is it necessary to expose the paths_strict element on the new
annotation
(https://github.com/apache/sling-org-apache-sling-servlets-annotations/blob/59471282a5d5364f4255af6dd27113c2c4f808ce/src/main/java/org/apache/sling/servlets/annotations/SlingServletPathsStrict.java#L72)
?
I think this should rather be write-protected. IMHO it doesn 't make any sense
to use annotation {{SlingServletPathsStrict}} and then disable strict handling.
Can't we use Meta annotations to set that property accordingly?
> Implement a new SlingServletPathsStrict annotation
> --------------------------------------------------
>
> Key: SLING-9055
> URL: https://issues.apache.org/jira/browse/SLING-9055
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Affects Versions: Sling Servlet Annotations 1.2.4
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: Sling Servlet Annotations 1.2.6, Servlets Resolver 2.6.6
>
>
> We need a new annotation to use the new {{sling.servlet.paths.strict}} mode
> introduced by SLING-8110, allowing to specify the extension, selectors and
> methods (all optional) that this mode takes into account.
> As discussed on the Sling dev list, this annotation should use a
> {{@Requirement}} meta-annotation [1] to generate an OSGi requirement for the
> version of the
> {{o.a.s.servlets.resolver}} bundle which includes this functionality.
> [1]
> https://osgi.org/specification/osgi.core/7.0.0/framework.api.html#org.osgi.annotation.bundle.Requirement
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
