November 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5545) Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5545: ------------------------------------- Typically when Olingo project releases then Teiid will pick up in following versions. We can't really control the Olingo schedule. Teiid releases every 2 months. Olingo dies not have a fixed schedule. If you want you can locally build Olingo and replace libraries in Teiid if you want right away. > Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header > -------------------------------------------------------------------------------------------------------- > > Key: TEIID-5545 > URL: https://issues.jboss.org/browse/TEIID-5545 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 12.0 > > > When using Teiid together with SAPUI5/OpenUI5 Odata V4 model, batch processing does not work as Teiid rejects the "Accept: multipart/mixed" header. The issue has been described in > https://developer.jboss.org/message/986421#986421 > It has been stated that Olingo in general does support multipart messages and it was recommended to remove the header from the request. > https://developer.jboss.org/message/986425#986425 > Unfortunately this seems to be not easily possible when using the SAPUI5 framework. I addressed the issue in the SAPUI5 forum under the following issue: > https://github.com/SAP/openui5/issues/2288 > The result of this discussion was, that the header is valid for the send content. As I am no expert in the topic I do not really have an opinion on that. However, > https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html > suggests that the header is required. So I am not sure if it is correct or an error to reject the message. However, if Olingo can process the content, it would be great to have a fix for the accept header, or alternatively a config option to enable handling of the Accept header in a way that Olingo processes these data. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5543) Configuration Option for default OData format

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5543?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5543: ------------------------------------- XML is falling out of choice in OData specification, so in future it may be just JSON or other formats. So, we will leave this as is then. > Configuration Option for default OData format > ---------------------------------------------- > > Key: TEIID-5543 > URL: https://issues.jboss.org/browse/TEIID-5543 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Optional > Fix For: 12.x > > > It would be great to have a config option to set the default format for odata responses which is chosen if no Accept header was set to request the format. > SapUI5 / OpenUI5 for example sends Accept * / * > Would be great if the admin could decide on the default format in such cases. > See related discussion https://developer.jboss.org/thread/279113 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5543) Configuration Option for default OData format

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5543?page=com.atlassian.jira.plugin... ] Christoph John commented on TEIID-5543: --------------------------------------- Hello Ramesh, my understanding was that I should add the ticket regarding the implementation of a switch option. I mentioned that json is fine as a default https://developer.jboss.org/message/986422#986422 > Configuration Option for default OData format > ---------------------------------------------- > > Key: TEIID-5543 > URL: https://issues.jboss.org/browse/TEIID-5543 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Optional > Fix For: 12.x > > > It would be great to have a config option to set the default format for odata responses which is chosen if no Accept header was set to request the format. > SapUI5 / OpenUI5 for example sends Accept * / * > Would be great if the admin could decide on the default format in such cases. > See related discussion https://developer.jboss.org/thread/279113 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5545) Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ] Christoph John commented on TEIID-5545: --------------------------------------- Hello, I am curious, if you wait till 4.6 release, in what time frame will the feature than become available in Teiid? I am not familiar with the release cycles of Olingo and Teiid. > Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header > -------------------------------------------------------------------------------------------------------- > > Key: TEIID-5545 > URL: https://issues.jboss.org/browse/TEIID-5545 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 12.0 > > > When using Teiid together with SAPUI5/OpenUI5 Odata V4 model, batch processing does not work as Teiid rejects the "Accept: multipart/mixed" header. The issue has been described in > https://developer.jboss.org/message/986421#986421 > It has been stated that Olingo in general does support multipart messages and it was recommended to remove the header from the request. > https://developer.jboss.org/message/986425#986425 > Unfortunately this seems to be not easily possible when using the SAPUI5 framework. I addressed the issue in the SAPUI5 forum under the following issue: > https://github.com/SAP/openui5/issues/2288 > The result of this discussion was, that the header is valid for the send content. As I am no expert in the topic I do not really have an opinion on that. However, > https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html > suggests that the header is required. So I am not sure if it is correct or an error to reject the message. However, if Olingo can process the content, it would be great to have a fix for the accept header, or alternatively a config option to enable handling of the Accept header in a way that Olingo processes these data. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5543) Configuration Option for default OData format

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5543?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5543: ------------------------------------- Ok, There is no support for JSON based metadata until 4.0.1 specification. Olingo does have an implementation for this but not full 4.0.1 support, so we would have to wait for that or help in implement the specification. > Configuration Option for default OData format > ---------------------------------------------- > > Key: TEIID-5543 > URL: https://issues.jboss.org/browse/TEIID-5543 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Optional > Fix For: 12.x > > > It would be great to have a config option to set the default format for odata responses which is chosen if no Accept header was set to request the format. > SapUI5 / OpenUI5 for example sends Accept * / * > Would be great if the admin could decide on the default format in such cases. > See related discussion https://developer.jboss.org/thread/279113 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5543) Configuration Option for default OData format

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5543?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5543: --------------------------------------- [~rareddy] the request here was specifically for the metadata, which currently defaults to xml. > Configuration Option for default OData format > ---------------------------------------------- > > Key: TEIID-5543 > URL: https://issues.jboss.org/browse/TEIID-5543 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Optional > Fix For: 12.x > > > It would be great to have a config option to set the default format for odata responses which is chosen if no Accept header was set to request the format. > SapUI5 / OpenUI5 for example sends Accept * / * > Would be great if the admin could decide on the default format in such cases. > See related discussion https://developer.jboss.org/thread/279113 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5548) Document the module name changes

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5548: ------------------------------------- Summary: Document the module name changes Key: TEIID-5548 URL: https://issues.jboss.org/browse/TEIID-5548 Project: Teiid Issue Type: Sub-task Components: thorntail Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 11.2.1 We should provide a short doc to describe the module name changes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5545) Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5545: --------------------------------------- Since it wasn't raised through customer support, I'd vote against a fork/patches. > Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header > -------------------------------------------------------------------------------------------------------- > > Key: TEIID-5545 > URL: https://issues.jboss.org/browse/TEIID-5545 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 12.0 > > > When using Teiid together with SAPUI5/OpenUI5 Odata V4 model, batch processing does not work as Teiid rejects the "Accept: multipart/mixed" header. The issue has been described in > https://developer.jboss.org/message/986421#986421 > It has been stated that Olingo in general does support multipart messages and it was recommended to remove the header from the request. > https://developer.jboss.org/message/986425#986425 > Unfortunately this seems to be not easily possible when using the SAPUI5 framework. I addressed the issue in the SAPUI5 forum under the following issue: > https://github.com/SAP/openui5/issues/2288 > The result of this discussion was, that the header is valid for the send content. As I am no expert in the topic I do not really have an opinion on that. However, > https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html > suggests that the header is required. So I am not sure if it is correct or an error to reject the message. However, if Olingo can process the content, it would be great to have a fix for the accept header, or alternatively a config option to enable handling of the Accept header in a way that Olingo processes these data. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5543) Configuration Option for default OData format

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5543?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5543. --------------------------------- Resolution: Cannot Reproduce >From my testing, when the Accept header is */* the code automatically already choosing to return the JSON as the preferred content type to return. If you want to write a sample code like in `IntegrationTestOData4` to prove this is not happening, we can re-open > Configuration Option for default OData format > ---------------------------------------------- > > Key: TEIID-5543 > URL: https://issues.jboss.org/browse/TEIID-5543 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Optional > Fix For: 12.x > > > It would be great to have a config option to set the default format for odata responses which is chosen if no Accept header was set to request the format. > SapUI5 / OpenUI5 for example sends Accept * / * > Would be great if the admin could decide on the default format in such cases. > See related discussion https://developer.jboss.org/thread/279113 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5536) Create separate repository for Thorntail modules

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5536?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5536. --------------------------------- Resolution: Done > Create separate repository for Thorntail modules > ------------------------------------------------ > > Key: TEIID-5536 > URL: https://issues.jboss.org/browse/TEIID-5536 > Project: Teiid > Issue Type: Task > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 11.2.1 > > > THORN-2232 Removes the Teiid modules from the core Thorntail repo for better release management. However, Teiid Thorntail would need a new home. > Most notable breaking change will be, the package names will change from that of Thorntail. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2018