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

I would like to come back on you regarding the Olingo topic. I have seen that Olingo 2.0.11 was released in February, and I hope that the next Teiid release 12.0.2 will include it. Is this planned?

I was therefore wondering, if there have been changes in the teiid-olingo-patches-X.jar file between version 11.2.0 and 12.1 that would make it infeasible to just copy the olingo library files over to the files included in teiid 12.1.

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.2 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.