[
https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIIDSB-65:
---------------------------------------
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.
I'm not sure why that is an issue. It's up to the service if there is any
additional context.
It's not a bad idea to have odata4 or a service name by default as the context if
there will be anything else available at that same host/port - whether static files, rest
access, yet another odata version, etc. If you don't want this as the default for
user driven spring boot that's fine, but it should be the default for anything
generated by the ui.
We do not need any. Previous auth redirects are currently supported
natively in Keycloak.
That's why I'm asking specifically about standalone, not openshift. Is there a
good ootb experience there with 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)