[JBoss JIRA] (TEIID-5614) Teiid Spring Boot - Enable Spring Actuator and non OData requests
by Tamar Meron (Jira)
Tamar Meron created TEIID-5614:
----------------------------------
Summary: 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: Steven Hawkins
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":
<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>
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_S...
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)
5 years, 12 months
[JBoss JIRA] (TEIID-5592) Update or deprecate teiid-quickstarts
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5592?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-5592:
------------------------------------
If we're going to split out the teiid-wildfly code and continue to support wildfly, should the teiid-quickstarts be moved to a similar repo: wildfly-teiid-quickstarts (to follow the naming as the others).
> Update or deprecate teiid-quickstarts
> -------------------------------------
>
> Key: TEIID-5592
> URL: https://issues.jboss.org/browse/TEIID-5592
> Project: Teiid
> Issue Type: Quality Risk
> Components: Quick Starts
> Reporter: Steven Hawkins
> Assignee: Van Halbert
> Priority: Major
> Fix For: 12.1
>
>
> The last update to the quickstarts was for Teiid 10 - which should have been largely compatible with Teiid 11. However this should be reviewed and updated for Teiid 11 - or we should deprecate them and update teiid.io appropriately.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 12 months
[JBoss JIRA] (TEIID-5613) upgrade to thorntail 2.3
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5613?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5613:
-------------------------------------
Did they update in a minor release to WF15?
> upgrade to thorntail 2.3
> ------------------------
>
> Key: TEIID-5613
> URL: https://issues.jboss.org/browse/TEIID-5613
> Project: Teiid
> Issue Type: Task
> Components: thorntail
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
>
> Thorntail with THORN-2126 has intermediate versions, such as the 1.5.3 config-api, on wildfly 14 - but moved to WildFly 15 for the release. I'll experiment a little if Teiid 12 is compatible enough to build Thorntail 2.3 support directly. More than likely though we'll need to wait until Teiid 13 to sync back up.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 12 months
[JBoss JIRA] (TEIID-5613) upgrade to thorntail 2.3
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5613:
-------------------------------------
Summary: upgrade to thorntail 2.3
Key: TEIID-5613
URL: https://issues.jboss.org/browse/TEIID-5613
Project: Teiid
Issue Type: Task
Components: thorntail
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 13.0
Thorntail with THORN-2126 has intermediate versions, such as the 1.5.3 config-api, on wildfly 14 - but moved to WildFly 15 for the release. I'll experiment a little if Teiid 12 is compatible enough to build Thorntail 2.3 support directly. More than likely though we'll need to wait until Teiid 13 to sync back up.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 12 months
[JBoss JIRA] (TEIID-5521) Add build plugins used by basepom to help with dependency handling
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5521?page=com.atlassian.jira.plugin... ]
Van Halbert edited comment on TEIID-5521 at 1/17/19 4:59 PM:
-------------------------------------------------------------
I assume release, you mean the final-release profile. I'll add the following:
{code}
<properties>
<basepom.check.skip-javadoc>false</basepom.check.skip-javadoc>
</properties>
{code}
updated my teiid-5521 branch.
was (Author: van.halbert):
I assume release, you mean the final-release profile. I'll add the following:
{code}
<properties>
<basepom.check.skip-javadoc>false</basepom.check.skip-javadoc>
</properties>
{code}
> Add build plugins used by basepom to help with dependency handling
> ------------------------------------------------------------------
>
> Key: TEIID-5521
> URL: https://issues.jboss.org/browse/TEIID-5521
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 12.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> Utilize plugins that basebom uses, which will help reduce half the headaches you go though during the productization with versions.
> plugins:
> * duplicate-finder-maven-plugin
> * maven-dependency-plugin
> * maven-dependency-versions-check-plugin
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 12 months
[JBoss JIRA] (TEIID-5521) Add build plugins used by basepom to help with dependency handling
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5521?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-5521:
------------------------------------
I assume release, you mean the final-release profile. I'll add the following:
{code}
<properties>
<basepom.check.skip-javadoc>false</basepom.check.skip-javadoc>
</properties>
{code}
> Add build plugins used by basepom to help with dependency handling
> ------------------------------------------------------------------
>
> Key: TEIID-5521
> URL: https://issues.jboss.org/browse/TEIID-5521
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 12.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> Utilize plugins that basebom uses, which will help reduce half the headaches you go though during the productization with versions.
> plugins:
> * duplicate-finder-maven-plugin
> * maven-dependency-plugin
> * maven-dependency-versions-check-plugin
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 12 months
[JBoss JIRA] (TEIID-5521) Add build plugins used by basepom to help with dependency handling
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5521?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5521:
-------------------------------------
It looks like basebom turns off the javadoc for the build. This needs to be turned back on for the release profile otherwise when you push to maven central it will fail.
> Add build plugins used by basepom to help with dependency handling
> ------------------------------------------------------------------
>
> Key: TEIID-5521
> URL: https://issues.jboss.org/browse/TEIID-5521
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 12.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> Utilize plugins that basebom uses, which will help reduce half the headaches you go though during the productization with versions.
> plugins:
> * duplicate-finder-maven-plugin
> * maven-dependency-plugin
> * maven-dependency-versions-check-plugin
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 12 months