Hi, On Thu, Mar 28, 2013 at 9:39 AM, Ian Boston <i...@tfd.co.uk> wrote: > Should I depend on a reference of a MicroKernel or a NodeStore when > constructing the Oak class (new > Oak(?).when(....).createContentRepositroy()) ?
It's better if you use the Oak(NodeStore) signature as that'll work also with the SegmentMK backend that implements just the NodeStore interface instead of MicroKernel. The Oak(MicroKernel) signature just wraps the given MicroKernel instance to a KernelNodeStore. > I see there are a number of providers in the oak-core bundle. Should I > use these to build the Oak class or is it Ok to build it from internal > instances ? You mean the OSGi services that oak-core provides? It's still a bit of an open question whether the core repository should be wired up entirely through OSGi or have some of the core components (security, node type validation, etc.) injected directly with Oak.with() as hardcoded parts. The latter approach (coupled with hooks to bring in also more dynamic OSGi services) might be better as it gives us more control over repository startup. BR, Jukka Zitting
