Konrad Windszus wrote > My use case is AEM: > I have an existing page containing some components (each one encapsulated in > dedicated child resources). > Now the underlying template in AEM is extended (i.e. new fixed components > have been added). For each of those a child resource is necessary, which does > not exist yet on older pages (being created at a point in time, where the > template did not have that component yet). > > In Sightly we include those new components via data-sly-use with an explicit > resourceType. Sightly will first try to get the child resource with that > path. If it does not exist yet it will create a SyntheticResource with the > given resource type. > For example to get the cloud service configuration we would need to get the > (existing) container AEM page for the SyntheticResource. This currently > fails, because of the issues mentioned. > > If this would work, the component would be rendered fine (even acting on a > SyntheticResource).
Ok, so I guess this can be easily solved in Sightly as this sounds to me like a Sightly use case. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
