You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2016/11/25 20:16:58 UTC
[jira] [Resolved] (SLING-6333) Context-Aware Config: Allow to mark
Config Annotation Classes as "Collections"
[ https://issues.apache.org/jira/browse/SLING-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert resolved SLING-6333.
-----------------------------------
Resolution: Fixed
Completed: At revision: 1771375
> Context-Aware Config: Allow to mark Config Annotation Classes as "Collections"
> ------------------------------------------------------------------------------
>
> Key: SLING-6333
> URL: https://issues.apache.org/jira/browse/SLING-6333
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Minor
> Labels: contextaware-config
> Fix For: Context-Aware Configuration API 1.0.2, Context-Aware Configuration SPI 1.2.0, Context-Aware Configuration Impl 1.2.0
>
>
> basically, configurations defined via annotation classes can be used for both single or collection configuration access. but in most cases it's only used for one or the other.
> we should add a "collection" property in the @Configuration annotation so annotation classes can be marked for their primary usage, and make this information accessible via the SPI and ConfigurationManager APIs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)