[ https://issues.apache.org/jira/browse/SLING-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845977#comment-17845977 ]
Stefan Seifert commented on SLING-12302: ---------------------------------------- for 1.: this looks like a bug, i assume that it probably not only affects HTL context, but in general. i think it would be worth creating a dedicated issue for it, probably with a unit test case, if possible. for 2: i'm not sure how much this syntax to fetch complex caconfigs directly from HTL is used in practice - probably not so much, esp. considering the fact you are the first asking that detailed questions after all that years it's available... i think there is no easy way to iterate over nested child lists, and currently we do not plan to add support for that, unless there is a high need. i think in most cases caconfigs are consumed in sling models, and consumed in HTL from there. a benefit of that approach is to use strong typing and compile-time check. > CA Config access syntax is inconsistent in HTL > ---------------------------------------------- > > Key: SLING-12302 > URL: https://issues.apache.org/jira/browse/SLING-12302 > Project: Sling > Issue Type: Bug > Reporter: Karol Lewandowski > Assignee: Stefan Seifert > Priority: Major > > I have a problem understanding how nested configs can be accessed in HTL or > if there is a bug in the implementation. > The > [documentation|https://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration.html#accessing-configuration-from-htlsightly-templates] > gives an example: > {{{}$\{caconfig['x.y.z.ConfigSample']['nestedConfig/stringParam']{}}}} > However, it doesn't work when a configuration annotation class is defined. > Steps to reproduce: > 1. Create a config node: > {{/conf/we-retail/sling:configs/us/en/sling:configs/com.mysite.core.config.TestConfig}} > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" > xmlns:jcr="http://www.jcp.org/jcr/1.0" > jcr:primaryType="sling:OsgiConfig" > email="t...@example.com" > enabled="{Boolean}true" > number="{Long}123"> > <nested > jcr:primaryType="sling:OsgiConfig" > greeting="hello"/> > </jcr:root> > {code} > and reference it from some path. > 2. Access in HTL without configuration annotation class: > {code} > Email: ${caconfig['com.mysite.core.config.TestConfig'].email} > Number: ${caconfig['com.mysite.core.config.TestConfig'].number} > Enabled: ${caconfig['com.mysite.core.config.TestConfig'].enabled} > Greeting (config path): > ${caconfig['com.mysite.core.config.TestConfig/nested'].greeting} > Greeting (property path): > ${caconfig['com.mysite.core.config.TestConfig']['nested/greeting']} {code} > This gives the output: > {code} > Email: t...@example.com > Number: 123 > Enabled: true > Greeting (config path): hello > Greeting (property path): hello {code} > It works as expected. > 3. Create annotation classes: > {code:java} > package com.mysite.core.config; > import org.apache.sling.caconfig.annotation.Configuration; > @Configuration > public @interface TestConfig { > String email(); > int number() default 5; > boolean enabled(); > NestedConfig nested(); > } > {code} > and > {code:java} > package com.mysite.core.config; > public @interface NestedConfig { > String greeting(); > } > {code} > The previous HTL will print: > {code} > Email: t...@example.com > Number: 123 > Enabled: true > Greeting (config path): hello > Greeting (property path): {code} > Accessing nested config value with property name path doesn't work. Is it > expected? > I'm working on support for CA Configs in AEM IDE, so I don't want to make it > work in my AEM application but provide the correct syntax support. -- This message was sent by Atlassian Jira (v8.20.10#820010)