[
https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIIDSB-65.
---------------------------------
Resolution: Done
The issue was in the calculation of the baseURI between various different paths. Also
since metadata gets cached the very first time, it can be any request.
Current Spring Boot supports
{code}
http://<h>:<p>
http://<h>:<p>/model
http://<h>:<p>/context
http://<h>:<p>/context/model
{code}
all for single VDB. Where user has the choice of setting the context (this really is SB
feature, we can not turn off), then "/model" option when user also wants to
expose at model level. By default "/" is at view model level, if there is only a
single physical model then it takes the place of View model level in terms of URL
handling.
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)