label, description and the optional additional properties are not used for configuration resolution or reading or writing configuration data. but they are passed through via the Management API and can be used by any application which uses this Sling caconfig Management API (e.g. the wcm.io config editor).
the values are stored in the classes, but are read only once when the bundle is deployed and the configuration classes are detected via the header value. stefan >-----Original Message----- >From: Konrad Windszus [mailto:[email protected]] >Sent: Monday, July 17, 2017 4:45 PM >To: [email protected] >Subject: Context-Aware configuration: Annotation evaluation in Sling > >Currently from reading the documentation at >https://sling.apache.org/documentation/bundles/context-aware- >configuration/context-aware-configuration.html it is not 100% clear what >advantage I do have by providing the annotation attributes "label" and >"description" for configuration interfaces. I assume those are currently >evaluated only by http://wcm.io/caconfig/editor/, i.e. not by Sling itself. > >Also I assume that those are runtime annotations which are not being >evaluated at compile time (except for the @Configuration itself which ends >up in the Sling-ContextAware-Configuration-Classes bundle header). Maybe we >can make a bit more explicit which parts of the annotations are currently >evaluated by which part of Sling in the documentation. That would help a >lot. >WDYT? >Konrad
