[teiid-issues] [JBoss JIRA] (TEIID-5614) Teiid Spring Boot - Enable Spring Actuator and non OData requests

[Ramesh Reddy (Jira)]

    [ https://issues.jboss.org/browse/TEIID-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685963#comment-13685963 ] 

Ramesh Reddy commented on TEIID-5614:
-------------------------------------

Looks like it is little quirky than I originally thought. In Actuator 1.x, the API at root context plus, Teiid used servlets to develop the OData API so that can code reuse from WildFly side. Here I suspect Actuator is using Spring MVC. I will able to redirect any servlet-based calls but when not a Spring MVC based requests.  Maybe I just need to leave it there for now, until we move up to Spring 2 and/or port OData stuff to Spring.

> Teiid Spring Boot - Enable Spring Actuator and non OData requests
> -----------------------------------------------------------------
>
>                 Key: TEIID-5614
>                 URL: https://issues.jboss.org/browse/TEIID-5614
>             Project: Teiid
>          Issue Type: Feature Request
>            Reporter: Tamar Meron
>            Assignee: Ramesh Reddy
>            Priority: Major
>
> While working with Teiid spring boot starter in my spring boot app I encountered an issue when trying to access spring actuator endpoints.
> I have "server.context-path: /api/odata" in my bootstrap.yml configuration.
> Then, accessing <my-server-url>/api/odata/health returns an error since I don't have a table named "health":
> {code}
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>null</code>
>   <message>
>         Cannot find EntitySet, Singleton, ActionImport or FunctionImport with name 'health'.
>   </message>
> </error>
> {code}
> I need to "split" the context for OData endpoints and for the rest endpoints which are not OData endpoints.
> I saw that Olingo has a support for that ("org.apache.olingo.odata2.path.split" property).
> (didn't find any documentation for that "split" for OData version 4)
> https://olingo.apache.org/doc/odata2/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html 
> Maybe this feature is useful also for requests which are not OData Protocol requests(and not only for Spring actuator endpoints..)



--
This message was sent by Atlassian Jira
(v7.12.1#712002)