Generated entryPoints value does not match CAP Java application configuration

[StefanHenke]

This item is mainly as preparation of a discussion happening next week about issues we currently have in CAP Java when leveraging the @cap-js/ord plugin.

CAP Java exposes the ORD document produced by the @cap-js/ord plugin via an endpoint in the CAP Java Service backend next to e.g. the EDMx model. The generated values for apiResources[n].entryPoints always starts with /odata/v4 which is also the default in CAP Java. However, applications can overwrite this as part of the application configuration. Application configuration is not necessarily part of artifacts that are available at build-time, but can be supplied as environment variables at deploy-time/run-time.

At the moment, we do a post processing when serving the document at runtime and apply the correct path. As this requires understanding of the ORD semantics, we are looking for a better approach. One possible way could be to provide a template option which allows a simple search and replace logic in the processing. We have existing cases in the CAP Java architecture where this is done in the EDMx handling.