[
https://issues.apache.org/jira/browse/SLING-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492672#comment-16492672
]
Carsten Ziegeler commented on SLING-7624:
-----------------------------------------
The annotations provided by the OSGi alliance in general go into a similar
direction, single purpose, simple annotations. Instead of having a single uber
annotation with 25 attributes, it's rather a larger set of annotations with one
or just a couple of attributes each.
In general, if things can be used independently, then we should have separate
annotations.
@SlingServletPrefix is a good example - imagine we would have the prefix in
both the Paths and the ResourceTypes annotation instead. Now a user can define
different values for the prefix in both annotations and use them on a service.
While you would expect that both prefix values are somehow used, in fact only
one is used. That's hard to explain and understand
> 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)