[
https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin...
]
Christoph John edited comment on TEIID-5545 at 1/3/19 11:57 AM:
----------------------------------------------------------------
Hello Ramesh,
very great news!!!! The Olingo update did work and OpenUI5 is now smoothly running in
batch mode, at least my first tests look like this :)
I am wondering, if there might be a chance to get you interested in extending the Olingo
behavior to support the early request feature of OpenUI5 as well. Then the entire OData
V4 functionality of OpenUI would be supported.
The early request feature seems to be a HEAD request which is send as soon as the model is
instantiated to async cache the metadata file/ files of the service for faster loading of
SPAs. The feature is described here:
https://sapui5.hana.ondemand.com/#/api/sap.ui.model.odata.v4.ODataModel
Search in the constructor for "earlyRequests?".
What I do not know is, if this feature is part of the official OData V4 Standard, or if
this is a SAP feature.
Once again, thanks for your help! Seems like I can really build an enterprise quality app
with open source components alone :)
was (Author: cjohn001):
Hello Ramesh,
very great news!!!! The Olingo update did work and OpenUI5 is now smoothly running in
batch mode, at least my first tests look like this :)
I am wondering, if there might be a chance to get you interested in extending the Olingo
behavior to support the early request feature of OpenUI5 as well. Then the entire OData
V4 functionality of OpenUI would be supported.
The early request feature seems to be a HEAD request which is send as soon as the model is
instantiated to async cache the metadata file/ files of the service for faster loading of
SPA apps. The feature is described here:
https://sapui5.hana.ondemand.com/#/api/sap.ui.model.odata.v4.ODataModel
Search in the constructor for "earlyRequests?".
What I do not know is, if this feature is part of the official OData V4 Standard, or if
this is a SAP feature.
Once again, thanks for your help! Seems like I can really build an enterprise quality app
with open source components alone :)
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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)