Since v13, as the default deployment option has changed from shared deployment (~v12) to separate deployments on each war.
This is normally fine in most use cases.
However, there is a corner case like this scenario:
- someone implemented a shared library which is supposed to be shared through api jar in shared classpath and implementation only in cms war;
- and their module also includes a custom classes used in a custom crisp resource resolver configuration.
- In this corner case, the crisp should be deployed as a 'shared' model like done before until v12 by placing crisp-api in shared, core/repository only in cms war, ... unless their library can be deployed onto each war separately.
Anyway, this issue is not about supporting the shared deployment model in documentation right now, which seems reasonable to do though...
In this ticket, I'd like CrispHstServices#getDefaultResourceServiceBroker() simply to fall back to HippoServiceRegistry.getService(ResourceServiceBroker.class) if it cannot find a "local" ResourceServiceBroker through hst component manager.