[
https://issues.apache.org/jira/browse/SLING-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473558#comment-16473558
]
Carsten Ziegeler commented on SLING-7624:
-----------------------------------------
I think the servlet name annotation should be a single value annotation so you
can write
@ServletName("foo") (of course the class name needs to follow the rules of the
property name)
For the others, wouldn't it make sense to split them as well? Both (path and
resource type) annotations have a "prefix" properrty, this could be a single
annotation (again single value), then the path annotation becomes a single
value annotation as well.
I'm not sure if the remaining properties of the resource type annotation should
be left inside a single one or be split up into several, so something like
@ResourceTypes("sling/type")
@Methods("post", "get")
(again the names of the annotations would be different according to the
property names)
> Add OSGi7 component property annotations for Servlet and Filter
> ---------------------------------------------------------------
>
> Key: SLING-7624
> URL: https://issues.apache.org/jira/browse/SLING-7624
> Project: Sling
> Issue Type: New Feature
> Components: Servlets
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> Previously there were annotations hosted at Felix for Sling Servlets/Filters
> as custom Felix SCR annotations
> (https://github.com/apache/felix/tree/trunk/tools/org.apache.felix.scr.annotations/src/main/java/org/apache/felix/scr/annotations/sling).
> With OSGi R7 and DS 1.4 component property annotations are specified. Sling
> should provide those annotations in a dedicated new artifact. Compare also
> with FELIX-5396.
> Those are supported in the upcoming bnd 4.0
> (https://github.com/bndtools/bnd/issues/2163).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
