[
https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIIDSB-65:
-------------------------------------
There are a couple of reasons I kept the default at the root as service root.
1) Simple root URL. Otherwise, we have to use something "/odata4" or
"vdb-name". The user needs to be educated about it.
2) One that works with JPA model as well as the VDB based model
3) In the OpenShift when the route is created you cannot create URL with context. That
means clicking on it will end up in always a 404.
Perhaps we could move "static" to a more obscure name, such that chance of
conflict is minimal?
OData include files are not being served correctly
--------------------------------------------------
Key: TEIIDSB-65
URL:
https://issues.jboss.org/browse/TEIIDSB-65
Project: Teiid Spring Boot
Issue Type: Bug
Components: OData
Affects Versions: 1.0.3
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Blocker
Fix For: 1.1.0
The include metadata files are not being served correctly through OData interface.
One of the reference is calculated as
http://rdbms-example-odata-teiid-dataservice.apps.garys-e21d.openshiftwor...
The class tries to request from this include url and this is what causes the 406 error
see $metadata int he URL
--
This message was sent by Atlassian Jira
(v7.12.1#712002)