I guess one of the problem's here is that there are parts which are not using the resource resolver and therefore start doing stuff before the resource bundles are active - and in that case the node types have not been added. I guess another solution would be to use the require/provide capabilities in the manifest.
Carsten 2014-07-23 11:04 GMT+02:00 Stefan Egli <stefane...@apache.org>: > It sounds like the core issue is that nodes are created before node types > are known? Could we tackle that specifically too? (Maybe that resolves the > situation) > > Cheers, > Stefan > > On 7/23/14 10:58 AM, "Bertrand Delacretaz" <bdelacre...@apache.org> wrote: > > >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