[JBoss JIRA] (TEIID-5594) Use generic rather than jboss javax dependencies for teiid core
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5594?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5594.
-----------------------------------
Resolution: Done
Thanks Van. Merged the PR with a minor change to use the non jboss slf4j - if that's needed we can switch back.
> Use generic rather than jboss javax dependencies for teiid core
> ---------------------------------------------------------------
>
> Key: TEIID-5594
> URL: https://issues.jboss.org/browse/TEIID-5594
> Project: Teiid
> Issue Type: Sub-task
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 12.1
>
>
> The following dependencies are aligned to Wildfly, but that is unnecessary for embedded/springboot. They should be replaced with more generic versions.
> {code}
> <dependency>
> <groupId>org.jboss.spec.javax.ws.rs</groupId>
> <artifactId>jboss-jaxrs-api_2.1_spec</artifactId>
> <version>1.0.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.xml.ws</groupId>
> <artifactId>jboss-jaxws-api_2.3_spec</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.servlet</groupId>
> <artifactId>jboss-servlet-api_3.1_spec</artifactId>
> <version>1.0.2.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.2_spec</artifactId>
> <version>1.1.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.spec.javax.xml.bind</groupId>
> <artifactId>jboss-jaxb-api_2.3_spec</artifactId>
> <version>1.0.1.Final</version>
> </dependency>
> <dependency>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-api</artifactId>
> <version>1.7.22.jbossorg-1</version>
> </dependency>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (TEIID-5613) upgrade to thorntail 2.3
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5613?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5613:
---------------------------------------
The last WildFly .Y release was 10.1 in 2016. They've only done a couple of ..Z minor releases, but otherwise a 3-4 month cadence for a major release after WildFly 11.
> 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, 5 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:
-------------------------------------
Maybe I am misreading 6 months to 3 months, that means they have no dot releases at all
> 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, 5 months
[JBoss JIRA] (TEIID-5613) upgrade to thorntail 2.3
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5613?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5613:
---------------------------------------
We are at about 6 months for major releases. In this case I didn't push further to WF 15 toward the end of the 12 cycle - Thorntail did. Also from 14 to 15 was only 3 months for WildFly.
> 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, 5 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:
-------------------------------------
WildFly has adjusted their rate of release of each major version to I believe every 6 months. We need to think of this release cadence and come up some strategy for Teiid.
> 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, 5 months
[JBoss JIRA] (TEIID-5614) Teiid Spring Boot - Enable Spring Actuator and non OData requests
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5614?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-5614:
--------------------------------
Description:
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_S...
Maybe this feature is useful also for requests which are not OData Protocol requests(and not only for Spring actuator endpoints..)
was:
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..)
> 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_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, 5 months
[JBoss JIRA] (TEIID-5614) Teiid Spring Boot - Enable Spring Actuator and non OData requests
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5614?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-5614:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> 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":
> <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, 5 months
[JBoss JIRA] (TEIID-5592) Update or deprecate teiid-quickstarts
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5592?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5592:
---------------------------------------
That would just be a renaming, which yes I can go ahead and do.
> 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, 5 months