[ https://issues.jboss.org/browse/TEIID-5536?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5536:
----------------------------------
Fix Version/s: 11.2.1
> 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)
[ https://issues.jboss.org/browse/TEIID-5537?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5537:
----------------------------------
Fix Version/s: 11.2.1
> Move Thorntail examples to use new modules
> ------------------------------------------
>
> Key: TEIID-5537
> URL: https://issues.jboss.org/browse/TEIID-5537
> Project: Teiid
> Issue Type: Sub-task
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 11.2.1
>
>
> Also, how about closing the "thorntail-examples" repo and merging the examples with the new Thontail repo?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[ https://issues.jboss.org/browse/TEIID-5543?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5543:
----------------------------------
Fix Version/s: 12.x
> 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)
[ https://issues.jboss.org/browse/TEIID-5544?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5544:
---------------------------------------
Taking ownership to get into 11.0.3 release.
> Comments in source model lead to vdb with erroneous annotation (Term attribute is missing)
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-5544
> URL: https://issues.jboss.org/browse/TEIID-5544
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 11.2
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.0
>
>
> A detailed description of the issue with an example of a wrongly generated metadata.xml can be found under the following link
> https://github.com/SAP/openui5/issues/2288
> In short: When a comment is added to an attribute in the source model, the generated annotation for the comment has the "Term" attribute missing. The Sapui5/ OpenUI5 library crashes when trying to parse the file.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[ https://issues.jboss.org/browse/TEIID-5544?page=com.atlassian.jira.plugin... ]
Work on TEIID-5544 started by Steven Hawkins.
---------------------------------------------
> Comments in source model lead to vdb with erroneous annotation (Term attribute is missing)
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-5544
> URL: https://issues.jboss.org/browse/TEIID-5544
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 11.2
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.0
>
>
> A detailed description of the issue with an example of a wrongly generated metadata.xml can be found under the following link
> https://github.com/SAP/openui5/issues/2288
> In short: When a comment is added to an attribute in the source model, the generated annotation for the comment has the "Term" attribute missing. The Sapui5/ OpenUI5 library crashes when trying to parse the file.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5545:
---------------------------------------
Olingo issue: https://issues.apache.org/jira/browse/OLINGO-1316
> 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: Steven Hawkins
> 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)
[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5545:
---------------------------------------
This is not a bug with the ContentNegotiator directly. It's an issue with the ServiceDispatcher ERROR logic.
> 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: Steven Hawkins
> 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)
[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5545:
---------------------------------------
[~rareddy] I agree this is an olingo issue. While I couldn't find any example showing the use of the Accept header with a batch request, the spec[1] does indicate:
A response to a batch request MUST contain a Content-Type header with value multipart/mixed.
So that implies Accept must be allowed/required to be multipart/mixed in the batch case. I'll provide an olingo pr.
[1] http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr...
> 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: Steven Hawkins
> 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)
[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5545:
----------------------------------
Fix Version/s: 12.0
> 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: Steven Hawkins
> 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)