An issue comes to light when testing certain odata implementations that do not handle a '/' being added to the end of the consumed URI, eg.
Use of the odata-connector on these services results in a malformed URI error.
Essentially, when the service URI is concatenated with the resource path, the constructed URI is appended with a '/' and a '?' prior to the addition of the query parameters.
This works fine for the reference odata implementation since can handle the extra '/'.
Since both teiid and the olingo4 tutorial use the olingo4 libraries, it would seem that the problem might be solved with them. However, it might be advantageous, given odata implementations already deployed, whether this odata-connector might check whether the '/' was supported before appending it?
(note. a bug report has been logged with the teiid project to this affect).