[
https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIIDSB-65:
-------------------------------------
Basically what we are talking about is what is the default behavior. My view is these
conflicts may happen in 1% of situations. The user can always add a context to avoid
conflicts.
It's that more of an issue of having a landing page?
It is
the service root. If one is copying and pasting this URL into fuse or any other
application for integration purpose they need to know to add the "/odata4"
otherwise it will end up in error. This should simply a little.
Also will you still need any of the /auth urls in standalone mode?
We do not need any. Previous auth redirects are currently supported natively in
Keycloak.
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)