> If we go for the approach where we use ORM + our own ClassLoaderService implementation, I think this method needs to change. It is not enough to just check whether the first loadJavaServices returns results. We need to call both loadJavaServices methods and then de-duplicate the results. A bit of a pita.

+1

> I am also tempted to say, that we should check in all of these methods the internalClassLoaderService first.

Actually wondering if - in case we know we're loading an internal extension/service which doesn't allow an override, we should not use the CLService but go via the well known parent classloaderservice. In case we want to lookup in both, then it would be correct to look for external overrides first?