Carsten Ziegeler wrote > Stefan Seifert wrote >>> a) If the value from the sling:confRef property ends with the bucket >>> name, then a warning is logged and this value is ignored >>> >>> b) If the value from the sling:confRef property is relative, the parent >>> hierarchy of the context resource is traversed up to find a context >>> resource with an absolute property. Once found, these are concatenated. >>> For example >>> /content/a >>> + sling:confRef=/conf/a >>> /content/a/b >>> + sling:confRef=b >>> >>> If you try to find configurations for /content/a/b it searches in >>> /conf/a/b first, then /conf/a >> >> ah, ok. >> from my side it would be ok to implement both directly in the >> DefaultConfigurationResourceResolvingStrategy, they sound reasonable. >> otherwise via the separate SPI for usecase b), usecase a) makes sense in any >> way. >> > Ok, thanks Stefan > > I'll create an issue and provide an implementation in > DefaultConfigurationResourceResolvingStrategy for both then. We can then > still decide whether we leave it like that or create the SPI > I've created SLING-6239 and SLING-6240
Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
