[
https://issues.apache.org/jira/browse/SLING-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15476849#comment-15476849
]
ASF GitHub Bot commented on SLING-6025:
---------------------------------------
GitHub user stefanseifert opened a pull request:
https://github.com/apache/sling/pull/170
SLING-6025 Context-Aware Config: Provide configuration parameter metadata
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stefanseifert/sling
feature/SLING-6025-config-metadata-bndplugin
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/170.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #170
----
commit 13fdd2873b6332c146bd703bf00820643a175a43
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-05T10:31:26Z
SLING-6025 provide configuration parameter metadata
commit 3a18bfa7f9e11b5eef29285e47e9be1f75e10fd3
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-05T12:18:04Z
SLING-6025 provide configuration parameter metadata
commit fdb469d17358ab59de2834c6938a5b71192153b7
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-05T14:07:31Z
SLING-6025 provide configuration parameter metadata
commit 06d557bbcdcf7eea1e9756dc1357144d96dd0fde
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-06T21:34:24Z
Merge branch 'trunk' into feature/SLING-6025-config-metadata
commit b5a4f9924e542ef05164431d6a0c10a2e17b24d0
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-06T21:37:35Z
adapt integration test to latest api changes
commit 6a711bb78ef62eda6ba24f049ab9199c13e3baca
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-08T13:13:11Z
Merge branch 'trunk' into feature/SLING-6025-config-metadata
commit 4c0e4bccb7cd213daa538e2274762b5fa3b5289d
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-08T14:41:46Z
SLING-6025 first steps bnd plugin
commit ef3ae533f7f974dd7da136fc960d08548caf8e29
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-08T16:00:42Z
SLING-6025 use asm
commit 6a87eec565066a5974ba6574da15f0f2957a1187
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-08T16:38:49Z
SLING-6025 generate only bundle header with configuration classes found
commit e2142679b38f6f7c0ee0aca49944b4d42f871e83
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-08T16:46:14Z
SLING-6025 change scope of error handling
commit c91e0bf846b40cf8771917f4ad7dddc2ae102ede
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-08T17:04:31Z
SLING-6025 bnd plugin integration test
commit d553910eae7727dea7dac0a98bee7d5c4b635bea
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-08T17:06:52Z
SLING-6025 bnd plugin integration test
commit 85352c73f7e88ec86f219189364f2be90d68c938
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-08T20:19:08Z
SLING-6025 bnd plugin integration test
commit 8ca49375764690beb4b5f5874d42f4a3ee43d86f
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-09T08:42:10Z
remove tooling from main build
commit 079b631e243b1199eb04291e0eb7e7002b59dfb6
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-09T09:16:03Z
SLING-6025 switch to configuration class header
commit c89cf087642ea1858612e418e4dda4e9e98697bc
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-09T10:38:42Z
SLING-6025 lazy initialization on bundle level
commit 1070d4d8ab1cf5fef5e918ca715b53729fb68e38
Author: sseifert <sseif...@pro-vision.de>
Date: 2016-09-09T11:22:23Z
SLING-6025 add name conflict check accross bundles
----
> Context-Aware Config: Provide configuration parameter metadata
> --------------------------------------------------------------
>
> Key: SLING-6025
> URL: https://issues.apache.org/jira/browse/SLING-6025
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: contextaware-config
> Fix For: Context-Aware Configuration 1.0.0
>
>
> in order to support configuration editors GUIs we need to provide metadata
> which configurations with parameter metadata are defined by the applications.
> this means:
> * list of all configurations registered (singleton, collections, nested) with
> ** their respective configuration names
> ** label (optional)
> ** description (optional)
> * list of all parameters for each configuration
> * parameter metadata:
> ** name
> ** type (only supported: String,int,long,double,boolean and arrays of them)
> ** label (optional)
> ** description (optional)
> ** default value
> ** further custom properties that may customized the configuration editor
> (e.g. widget type to use, optional)
> the applications needs a possibility to provide such configuration+parameter
> metadata. by default the annotation interface classes are used for this. they
> have to be detected on the runtime in the classpath when a new bundle is
> deployed using an osgi extender pattern (quite similar to sling models). to
> the annotation classes further annotations can be applied an class and
> property level to provide the additional metadata (label, description etc.).
> currently we can only support automatic detection of parameter metadata for
> configurations which are defined and accessed with annotation classes, not
> when the application used direct valuemap access or the low-level
> ConfigurationResourceResolver.
> by making the configuration metadata provider pluggable via an SPI we can
> ship the default configuration providing metadata detected from the deployed
> annotation classes, but leave a door open to add other sources as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
