Essentially, after replacing the olingo4 component in the context to bypass the null serviceUri issue, the route moves on to initialising the Olingo4Consumer. The latter tests the 'read' method to ensure all properties have been set (1). However, this fails due to the properties 'edm' and 'responseHandler' being missing.
Have come up with a test (2) that demonstrates the problem.
These properties are not documented (since they appear to be output properties). However
, they are added into the property names collection of the endpoint (3). This collection is compared against the method signatures in the Olingo4AppEndpointConfiguration and neither s/getEdm or s/getResponseHandler exist hence the exception thrown.