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