Default engine for embedded rest api

Camunda 7 Topics Discussion & Questions
,
1

This is a feature request.

We are embedding the rest api and the admin app in the many applications. The admin app brings its own ProcessEngineProvider. For the rest api we use our own, which has the convenience of serving a single engine as the “default” engine. Thus we don’t need to adapt the endpoints (/engine/engine-name/…) for each app.

@Override
public ProcessEngine getDefaultProcessEngine() {
    if (ProcessEngines.getProcessEngines().size() == 1) {
        return ProcessEngines.getProcessEngines().values().iterator().next();
    }
    return ProcessEngines.getDefaultProcessEngine(false);
}

The EngineUtil only picks up one of the ProcessEngineProvider (that happens to come first). Which in some cases (for us) is the one provided by the admin app.
It would be nice if EngineUtil (like ProcessEnginesFilter does) would also choose a single engine as the default. Alternatively it could iterate all providers from the service-loader (at least when engineName == null).

I hope that was clear. If not, please don’t hesitate to ask.

Thanks in advance!