3 Replies Latest reply on Jan 2, 2019 8:29 AM by cjohn001

Howto Configure Teiid Wildfly to use Odata V2 protocol version instead of V4

cjohn001 Dec 31, 2018 10:30 PM

Hello together,

I think the topic says already everything. I am currently using Teiid 9 and Teiid 11.2 Wildfly. Both by default use OData V4 Protocol. As I am currently working with a client side odata library for which OData V4 is highly experimental, I am trying to configure Teiid to speak OData V2 instead. So far I have not found a config option or description on how to achieve this. I am even not sure if I can expect an config option. Might it be that I have to replace

teiid-olingo-odata4.war

with something like teiid-olingo-odata2.war

In that case, where can I find the required war file ? Every help is welcome. Thanks a lot and happy new year

Best regards,

Christoph

1. Re: Howto Configure Teiid Wildfly to use Odata V2 protocol version instead of V4

cjohn001 Jan 1, 2019 9:01 PM (in response to cjohn001)

Well, I have found another discussion in the forum here, which mentions that there is not such a thing like a config option to switch to v4 and the only option would be to use the old and unmaintained v2 sources. Well, this is not a future prove alternative for me. Hence my question is answered.
Actions
2. Re: Howto Configure Teiid Wildfly to use Odata V2 protocol version instead of V4

shawkins Jan 2, 2019 7:43 AM (in response to cjohn001)

You can go to a legacy version of Teiid that includes OData V2 before [TEIID-3754] Remove OData V2 implementation of the Server - JBoss Issue Tracker such as Teiid 9.0.6 Maven Repository: org.jboss.teiid » teiid » 9.0.6 and try your scenario. If it works and you have sufficient motivation, then the v2 implementation could be forward ported to Teiid latest.
Actions
3. Re: Howto Configure Teiid Wildfly to use Odata V2 protocol version instead of V4

cjohn001 Jan 2, 2019 8:29 AM (in response to shawkins)

Hello Steven,

thanks for your feedback! However, as it seems that there is an undefinable amount of work involved in both solutions:

1. Working around the OpenUI5 issues client side and keeping Odata V4 or

2. Switching to OData V2 and doing the porting there and using the stable OpenUI5 implementation.

I think the more future proof solution is to solve issues on client side. I hope I will get some support from the SAP guys on these topics. Unfortunately their help forum seems to be not that greatly maintained like the one here. So I will first see how far I come with it.

Best regards,

Christoph
Actions

Go to original post