Konrad Windszus

The problem here is not the wildcard at the end, but the name `21c` which is not a valid name in XML ( https://www.w3.org/TR/REC-xml/#NT-NameStartChar). It needs to be escaped according...

@Vocinglero Without wildcard there is no query involved, therefore you need the wildcard to trigger it.

The same config is being used for https://github.com/Netcentric/accesscontroltool/blob/develop/docs/ApplyConfig.md#startup-hook, though.

> It then might just be a matter of explaining this; possibly improving the documentation. This OSGi configuration is not documented at all, so hopefully no one deviates from the...

The issue seems to be the evolution of the AEMaaCS build pipeline as outlined in https://adapt.to/2023/schedule/evolution-of-the-aemaacs-build-pipeline. 1. The build image step does no longer involve custom code 2. During the...

DocView is XML 1.0 (not 1.1). Therefore the XML 1.0 compliant escaping should be done: https://commons.apache.org/proper/commons-lang/apidocs/org/apache/commons/lang3/StringEscapeUtils.html#escapeXml10-java.lang.String- (not the one for 1.1 which includes control characters!

According to https://docs.mktossl.com/docs/experience-manager-cloud-service/content/operations/indexing.html?lang=en#index-names the pattern needs to be `.--custom-`

The pattern without product version makes a lot more sense to me. Thanks for pointing out the discrepancies in the documentation. If this version does not emit any warning in...

@diogopedreira Have you tried to deploy with the node name as proposed in this PR? Does it emit any warnings in CloudManager?

The unmodified index definition does no longer emit any issue in the code checks in Cloud Manager, therefore no need to change it right now.