Not sure if we really need that. Agreed, we now have a case where this is a problem - but why not just fix this? In the past we didn't have that problem.
Now, *if* we want to do something about it, why not have this as a configuration of the resource resolver factory? Before it registers itself it makes sure that the required resources are created/available. No need for additional services or dependencies. Carsten 2014-07-23 10:58 GMT+02:00 Bertrand Delacretaz <bdelacre...@apache.org>: > Hi, > > As SLING-3618 shows, there's some non-deterministic behavior in the > Sling startup that potentially causes nodes such as /var to be created > by different modules depending on startup timing. So potentially with > different node types, as seen in that issue. > > Does someone have a better idea on how to manage the creation of those > commonly used nodes? It's probably only about a handful of them such > as /var /libs /apps. > > We might define a CommonResourcesCreator service on which components > such as ClassLoaderWriterImpl depend. That service then makes sure the > required node types are available, and provides them to its clients. > > -Bertrand > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
