]
Ramesh Reddy commented on TEIID-5545:
-------------------------------------
Happy New Year to you too Christoph.
Basically you want to build Olingo project locally using maven build tool
{code}
/oilingo/mvn clean install
{code}
It will produce the jar files in the `target` directories. You would need to replace the
new JAR files with old ones in the WildFly distribution and making sure that the names
match. The one caveat is if at all Olingo changed any dependency modules or API then more
code on Teiid needs to be modified, this only can be determined after comparing both
versions.
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.1
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.