Hi Dmitry, Wonder if you would mind looking at this issue as well, please. Again, I may been misunderstanding something but I just cannot make headway.
So have come up with a test[1] that demonstrates the problem. Essentially, after replacing the 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 [2]. However, this fails due to the properties 'edm' and 'responseHandler' being missing. 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. If you want any help in trying to solve either of the issues I've raised then let me know as I've had my head in them for a couple of days now. Thanks and regards Paul [1] https://gist.github.com/phantomjinx/90ee08a989ddff4366d792cc621b36a9#file-properties-issue-java [2] https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/util/component/ApiConsumerHelper.java#L55 [3] https://github.com/apache/camel/blob/master/components/camel-olingo4/camel-olingo4-component/src/main/java/org/apache/camel/component/olingo4/Olingo4Endpoint.java#L150 -- Paul Richardson * “Confronted by the great record of this country, and the tremendous promise of its future, all they do is croak, ‘socialism.’" Harry Truman
signature.asc
Description: OpenPGP digital signature
