[jira] [Commented] (OLINGO-1378) $search does not allow some special characters in search term
[
https://issues.apache.org/jira/browse/OLINGO-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159676#comment-17159676
]
Ramya commented on OLINGO-1378:
---
This is fixed as part of commit
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=7e1aa94d4e05540e2c183e912afbedb3501dc083
> $search does not allow some special characters in search term
> -
>
> Key: OLINGO-1378
> URL: https://issues.apache.org/jira/browse/OLINGO-1378
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
>Affects Versions: (Java) V4 4.0.0
>Reporter: Prakash Sagadevan
>Priority: Major
>
> OLINGO 4.4.0 $search does not allow to search for special chars, eg. # & | ".
> *Example:*
> {code:java}
> http://host/service/Products?$search=#bike
> {code}
> {code:java}
> http://host/service/Products?$search=bike & car
> {code}
> {code:java}
> http://host/service/Products?$search=bike | car
> {code}
> {code:java}
> http://host/service/Products?$search=""bike car""
> {code}
> OData Accept the below character in $search system query
> ||Symbol||Character||
> |A..Z|Capital Alphabet|
> |a..z|Small Alphabet|
> |0..9|Numbers|
> |-|Hyphen|
> |.|Dot|
> |_|Under scope|
> |~|Tilde|
> |!|Not symbol|
> |(|Open parentheses|
> |)|Close parentheses|
> |*|Star|
> |+|Plus|
> |,|Comma|
> |;|Semicolon|
> |:|Colon|
> |@|Email|
> |/|Slash|
> |$|Dollar|
> |'|Single quotes|
> |=|Equal|
> |%|Percentage|
> | |Space|
> |\t|Tab|
> we are getting the issue in below special character,
> ||Symbol|
> |#|
> |&|
> |||
> |"|
> Workaround: Double encoded above special characters.
> {code:java}
> http://host/service/Products?$search=%2523bike
> http://host/service/Products?$search=bike %2526 car
> http://host/service/Products?$search=bike %257C car
> http://host/service/Products?$search="%2522bike car%2522"
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (OLINGO-1378) $search does not allow some special characters in search term
[
https://issues.apache.org/jira/browse/OLINGO-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramya resolved OLINGO-1378.
---
Resolution: Fixed
> $search does not allow some special characters in search term
> -
>
> Key: OLINGO-1378
> URL: https://issues.apache.org/jira/browse/OLINGO-1378
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
>Affects Versions: (Java) V4 4.0.0
>Reporter: Prakash Sagadevan
>Priority: Major
>
> OLINGO 4.4.0 $search does not allow to search for special chars, eg. # & | ".
> *Example:*
> {code:java}
> http://host/service/Products?$search=#bike
> {code}
> {code:java}
> http://host/service/Products?$search=bike & car
> {code}
> {code:java}
> http://host/service/Products?$search=bike | car
> {code}
> {code:java}
> http://host/service/Products?$search=""bike car""
> {code}
> OData Accept the below character in $search system query
> ||Symbol||Character||
> |A..Z|Capital Alphabet|
> |a..z|Small Alphabet|
> |0..9|Numbers|
> |-|Hyphen|
> |.|Dot|
> |_|Under scope|
> |~|Tilde|
> |!|Not symbol|
> |(|Open parentheses|
> |)|Close parentheses|
> |*|Star|
> |+|Plus|
> |,|Comma|
> |;|Semicolon|
> |:|Colon|
> |@|Email|
> |/|Slash|
> |$|Dollar|
> |'|Single quotes|
> |=|Equal|
> |%|Percentage|
> | |Space|
> |\t|Tab|
> we are getting the issue in below special character,
> ||Symbol|
> |#|
> |&|
> |||
> |"|
> Workaround: Double encoded above special characters.
> {code:java}
> http://host/service/Products?$search=%2523bike
> http://host/service/Products?$search=bike %2526 car
> http://host/service/Products?$search=bike %257C car
> http://host/service/Products?$search="%2522bike car%2522"
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (OLINGO-1469) OData V4: Convert java.time types to correct Edm types
[ https://issues.apache.org/jira/browse/OLINGO-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1469. - > OData V4: Convert java.time types to correct Edm types > -- > > Key: OLINGO-1469 > URL: https://issues.apache.org/jira/browse/OLINGO-1469 > Project: Olingo > Issue Type: Bug >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Map java.Time.LocalDate to Edm.Date > java.Time.LocalTime to Edm.Time > java.Time.ZonedDateTime to Edm.DateTimeOffset > These changes have to be done in EdmTypeInfo.determineTypeKind -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1469) OData V4: Convert java.time types to correct Edm types
[ https://issues.apache.org/jira/browse/OLINGO-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1469. --- Resolution: Fixed > OData V4: Convert java.time types to correct Edm types > -- > > Key: OLINGO-1469 > URL: https://issues.apache.org/jira/browse/OLINGO-1469 > Project: Olingo > Issue Type: Bug >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Map java.Time.LocalDate to Edm.Date > java.Time.LocalTime to Edm.Time > java.Time.ZonedDateTime to Edm.DateTimeOffset > These changes have to be done in EdmTypeInfo.determineTypeKind -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1469) OData V4: Convert java.time types to correct Edm types
[ https://issues.apache.org/jira/browse/OLINGO-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159670#comment-17159670 ] Ramya commented on OLINGO-1469: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=6bc0fc72e66524515034037c0932e8a22a806a53 > OData V4: Convert java.time types to correct Edm types > -- > > Key: OLINGO-1469 > URL: https://issues.apache.org/jira/browse/OLINGO-1469 > Project: Olingo > Issue Type: Bug >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Map java.Time.LocalDate to Edm.Date > java.Time.LocalTime to Edm.Time > java.Time.ZonedDateTime to Edm.DateTimeOffset > These changes have to be done in EdmTypeInfo.determineTypeKind -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1469) OData V4: Convert java.time types to correct Edm types
Ramya created OLINGO-1469: - Summary: OData V4: Convert java.time types to correct Edm types Key: OLINGO-1469 URL: https://issues.apache.org/jira/browse/OLINGO-1469 Project: Olingo Issue Type: Bug Affects Versions: (Java) V4 4.7.1 Reporter: Ramya Assignee: Ramya Map java.Time.LocalDate to Edm.Date java.Time.LocalTime to Edm.Time java.Time.ZonedDateTime to Edm.DateTimeOffset These changes have to be done in EdmTypeInfo.determineTypeKind -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1362) OData V2: Missed http status code 420
[ https://issues.apache.org/jira/browse/OLINGO-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159666#comment-17159666 ] Ramya commented on OLINGO-1362: --- Added few more status codes https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=fcb643fdfdf3d05e001b5905d1f040371e588523 > OData V2: Missed http status code 420 > - > > Key: OLINGO-1362 > URL: https://issues.apache.org/jira/browse/OLINGO-1362 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.11 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Http status code 420 is not listed in > org/apache/olingo/odata2/api/commons/HttpStatusCodes.java > 420 http status code is a deprecated response and also it used to be the > return code for Twitter Search and Trends API when the client is being rate > limited. This 420 status code is not added in the olingo HttpStatusCodes and > hence the applications get 500 Internal server error. > (https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1176) OData V2.0: Code Improvements
[ https://issues.apache.org/jira/browse/OLINGO-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159661#comment-17159661 ] Ramya commented on OLINGO-1176: --- Code improvement as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=c0bb91129edf28bfea8adc347dc6985cf38c019f > OData V2.0: Code Improvements > - > > Key: OLINGO-1176 > URL: https://issues.apache.org/jira/browse/OLINGO-1176 > Project: Olingo > Issue Type: Bug >Affects Versions: V2 2.0.9 >Reporter: Ramya >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1446) Allow empty parameters for actions and action imports when there is no non binding parameter defined
[ https://issues.apache.org/jira/browse/OLINGO-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084717#comment-17084717 ] Ramya commented on OLINGO-1446: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=ddaab6b0fa6778869f03edc8d10dcf933098242b > Allow empty parameters for actions and action imports when there is no non > binding parameter defined > > > Key: OLINGO-1446 > URL: https://issues.apache.org/jira/browse/OLINGO-1446 > Project: Olingo > Issue Type: New Feature > Components: odata4-server >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > According to the OData v4 spec, section 11.5.5.1: > 4.01 services MUST support invoking actions with no non-binding parameters > and parameterless action imports both without a request body and with a > request body representing no parameters, according to the particular format. > Interoperable clients SHOULD always include a request body, even when > invoking actions with no non-binding parameters and parameterless action > imports. > When action does not have any non binding parameters, the client sends an > empty request body(AbstractODataInvokeRequest.getPayload()). > Olingo's server part, however, rejects an empty request body (see > ODataJsonDeserializer.parseJsonTree(InputStream)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OLINGO-1446) Allow empty parameters for actions and action imports when there is no non binding parameter defined
[ https://issues.apache.org/jira/browse/OLINGO-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1446. - > Allow empty parameters for actions and action imports when there is no non > binding parameter defined > > > Key: OLINGO-1446 > URL: https://issues.apache.org/jira/browse/OLINGO-1446 > Project: Olingo > Issue Type: New Feature > Components: odata4-server >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > According to the OData v4 spec, section 11.5.5.1: > 4.01 services MUST support invoking actions with no non-binding parameters > and parameterless action imports both without a request body and with a > request body representing no parameters, according to the particular format. > Interoperable clients SHOULD always include a request body, even when > invoking actions with no non-binding parameters and parameterless action > imports. > When action does not have any non binding parameters, the client sends an > empty request body(AbstractODataInvokeRequest.getPayload()). > Olingo's server part, however, rejects an empty request body (see > ODataJsonDeserializer.parseJsonTree(InputStream)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1446) Allow empty parameters for actions and action imports when there is no non binding parameter defined
[ https://issues.apache.org/jira/browse/OLINGO-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1446. --- Resolution: Fixed > Allow empty parameters for actions and action imports when there is no non > binding parameter defined > > > Key: OLINGO-1446 > URL: https://issues.apache.org/jira/browse/OLINGO-1446 > Project: Olingo > Issue Type: New Feature > Components: odata4-server >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > According to the OData v4 spec, section 11.5.5.1: > 4.01 services MUST support invoking actions with no non-binding parameters > and parameterless action imports both without a request body and with a > request body representing no parameters, according to the particular format. > Interoperable clients SHOULD always include a request body, even when > invoking actions with no non-binding parameters and parameterless action > imports. > When action does not have any non binding parameters, the client sends an > empty request body(AbstractODataInvokeRequest.getPayload()). > Olingo's server part, however, rejects an empty request body (see > ODataJsonDeserializer.parseJsonTree(InputStream)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1446) Allow empty parameters for actions and action imports when there is no non binding parameter defined
Ramya created OLINGO-1446: - Summary: Allow empty parameters for actions and action imports when there is no non binding parameter defined Key: OLINGO-1446 URL: https://issues.apache.org/jira/browse/OLINGO-1446 Project: Olingo Issue Type: New Feature Components: odata4-server Affects Versions: (Java) V4 4.7.1 Reporter: Ramya Assignee: Ramya According to the OData v4 spec, section 11.5.5.1: 4.01 services MUST support invoking actions with no non-binding parameters and parameterless action imports both without a request body and with a request body representing no parameters, according to the particular format. Interoperable clients SHOULD always include a request body, even when invoking actions with no non-binding parameters and parameterless action imports. When action does not have any non binding parameters, the client sends an empty request body(AbstractODataInvokeRequest.getPayload()). Olingo's server part, however, rejects an empty request body (see ODataJsonDeserializer.parseJsonTree(InputStream)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1443) Streaming support for Media types
[ https://issues.apache.org/jira/browse/OLINGO-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1443. --- Resolution: Fixed > Streaming support for Media types > - > > Key: OLINGO-1443 > URL: https://issues.apache.org/jira/browse/OLINGO-1443 > Project: Olingo > Issue Type: New Feature >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > In order to implement streaming of media resources it must be possible to > stream content through olingo directly without the need to store the content > in memory. > This has to be enabled for both read and write operations -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1442) Support update requests on Stream properties
[ https://issues.apache.org/jira/browse/OLINGO-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1442. --- Resolution: Fixed > Support update requests on Stream properties > > > Key: OLINGO-1442 > URL: https://issues.apache.org/jira/browse/OLINGO-1442 > Project: Olingo > Issue Type: New Feature >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per odata v4.01 specification, > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateStreamValues > A successful PUT request to the edit URL of a stream property changes the > media stream associated with that property. > The request body MUST contain the new media value for the stream whose media > type MUST be specified in a Content-Type header. > Currently library does not accept content-type headers other than > application/json. > Requests of the below form should be supported > PUT : > http://localhost:8081/odata-server-tecsvc/odata.svc/ESWithStream(7)/PropertyStream > Request Header : Content-Type : image/jpeg > Request-Body: Image file > The response Content-Type header should be same as that of the Content-Type > header specified in the request. If the prefer header is representation, then > the image should be in the response body -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1443) Streaming support for Media types
[ https://issues.apache.org/jira/browse/OLINGO-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17074314#comment-17074314 ] Ramya commented on OLINGO-1443: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=1c8e5ce60bf7c3f8ea4074f191b5c64eaf51b45d > Streaming support for Media types > - > > Key: OLINGO-1443 > URL: https://issues.apache.org/jira/browse/OLINGO-1443 > Project: Olingo > Issue Type: New Feature >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > In order to implement streaming of media resources it must be possible to > stream content through olingo directly without the need to store the content > in memory. > This has to be enabled for both read and write operations -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1443) Streaming support for Media types
Ramya created OLINGO-1443: - Summary: Streaming support for Media types Key: OLINGO-1443 URL: https://issues.apache.org/jira/browse/OLINGO-1443 Project: Olingo Issue Type: New Feature Affects Versions: (Java) V4 4.7.1 Reporter: Ramya Assignee: Ramya In order to implement streaming of media resources it must be possible to stream content through olingo directly without the need to store the content in memory. This has to be enabled for both read and write operations -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1442) Support update requests on Stream properties
[ https://issues.apache.org/jira/browse/OLINGO-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17074279#comment-17074279 ] Ramya commented on OLINGO-1442: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=225bc34dd9d49c17a3c226d97131a8dce6364d94 > Support update requests on Stream properties > > > Key: OLINGO-1442 > URL: https://issues.apache.org/jira/browse/OLINGO-1442 > Project: Olingo > Issue Type: New Feature >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per odata v4.01 specification, > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateStreamValues > A successful PUT request to the edit URL of a stream property changes the > media stream associated with that property. > The request body MUST contain the new media value for the stream whose media > type MUST be specified in a Content-Type header. > Currently library does not accept content-type headers other than > application/json. > Requests of the below form should be supported > PUT : > http://localhost:8081/odata-server-tecsvc/odata.svc/ESWithStream(7)/PropertyStream > Request Header : Content-Type : image/jpeg > Request-Body: Image file > The response Content-Type header should be same as that of the Content-Type > header specified in the request. If the prefer header is representation, then > the image should be in the response body -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OLINGO-1442) Support update requests on Stream properties
[ https://issues.apache.org/jira/browse/OLINGO-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya updated OLINGO-1442: -- Summary: Support update requests on Stream properties (was: OData V4: Suport update requests on Stream properties) > Support update requests on Stream properties > > > Key: OLINGO-1442 > URL: https://issues.apache.org/jira/browse/OLINGO-1442 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per odata v4.01 specification, > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateStreamValues > A successful PUT request to the edit URL of a stream property changes the > media stream associated with that property. > The request body MUST contain the new media value for the stream whose media > type MUST be specified in a Content-Type header. > Currently library does not accept content-type headers other than > application/json. > Requests of the below form should be supported > PUT : > http://localhost:8081/odata-server-tecsvc/odata.svc/ESWithStream(7)/PropertyStream > Request Header : Content-Type : image/jpeg > Request-Body: Image file > The response Content-Type header should be same as that of the Content-Type > header specified in the request. If the prefer header is representation, then > the image should be in the response body -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OLINGO-1442) Support update requests on Stream properties
[ https://issues.apache.org/jira/browse/OLINGO-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya updated OLINGO-1442: -- Affects Version/s: (Java) V4 4.7.1 > Support update requests on Stream properties > > > Key: OLINGO-1442 > URL: https://issues.apache.org/jira/browse/OLINGO-1442 > Project: Olingo > Issue Type: New Feature >Affects Versions: (Java) V4 4.7.1 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per odata v4.01 specification, > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateStreamValues > A successful PUT request to the edit URL of a stream property changes the > media stream associated with that property. > The request body MUST contain the new media value for the stream whose media > type MUST be specified in a Content-Type header. > Currently library does not accept content-type headers other than > application/json. > Requests of the below form should be supported > PUT : > http://localhost:8081/odata-server-tecsvc/odata.svc/ESWithStream(7)/PropertyStream > Request Header : Content-Type : image/jpeg > Request-Body: Image file > The response Content-Type header should be same as that of the Content-Type > header specified in the request. If the prefer header is representation, then > the image should be in the response body -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1442) OData V4: Suport update requests on Stream properties
Ramya created OLINGO-1442: - Summary: OData V4: Suport update requests on Stream properties Key: OLINGO-1442 URL: https://issues.apache.org/jira/browse/OLINGO-1442 Project: Olingo Issue Type: New Feature Reporter: Ramya Assignee: Ramya As per odata v4.01 specification, http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateStreamValues A successful PUT request to the edit URL of a stream property changes the media stream associated with that property. The request body MUST contain the new media value for the stream whose media type MUST be specified in a Content-Type header. Currently library does not accept content-type headers other than application/json. Requests of the below form should be supported PUT : http://localhost:8081/odata-server-tecsvc/odata.svc/ESWithStream(7)/PropertyStream Request Header : Content-Type : image/jpeg Request-Body: Image file The response Content-Type header should be same as that of the Content-Type header specified in the request. If the prefer header is representation, then the image should be in the response body -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OLINGO-1437) Add additional properties to OData Server Error
[ https://issues.apache.org/jira/browse/OLINGO-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1437. - > Add additional properties to OData Server Error > --- > > Key: OLINGO-1437 > URL: https://issues.apache.org/jira/browse/OLINGO-1437 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > OData error response can contain some additional fields: > @Common.longtextUrl > @Common.numericSeverity (only within details section) > @Common.additionalTargets > Olingo does not provide a way to specify these additional properties in > either ODataServerError or ODataErrorDetail. > Implementation detail: > Add an API setAdditionalProperties and getAdditionalProperties in > ODataServerError and ODataErrorDetail which allows to add these additional > properties. > The ODataErrorSerializer should serialize this additional properties and form > a correct json response. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1437) Add additional properties to OData Server Error
[ https://issues.apache.org/jira/browse/OLINGO-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1437. --- Resolution: Fixed > Add additional properties to OData Server Error > --- > > Key: OLINGO-1437 > URL: https://issues.apache.org/jira/browse/OLINGO-1437 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > OData error response can contain some additional fields: > @Common.longtextUrl > @Common.numericSeverity (only within details section) > @Common.additionalTargets > Olingo does not provide a way to specify these additional properties in > either ODataServerError or ODataErrorDetail. > Implementation detail: > Add an API setAdditionalProperties and getAdditionalProperties in > ODataServerError and ODataErrorDetail which allows to add these additional > properties. > The ODataErrorSerializer should serialize this additional properties and form > a correct json response. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1437) Add additional properties to OData Server Error
[ https://issues.apache.org/jira/browse/OLINGO-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062291#comment-17062291 ] Ramya commented on OLINGO-1437: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=a3318beed39dd92d887a953a07cf815693df8188 > Add additional properties to OData Server Error > --- > > Key: OLINGO-1437 > URL: https://issues.apache.org/jira/browse/OLINGO-1437 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > OData error response can contain some additional fields: > @Common.longtextUrl > @Common.numericSeverity (only within details section) > @Common.additionalTargets > Olingo does not provide a way to specify these additional properties in > either ODataServerError or ODataErrorDetail. > Implementation detail: > Add an API setAdditionalProperties and getAdditionalProperties in > ODataServerError and ODataErrorDetail which allows to add these additional > properties. > The ODataErrorSerializer should serialize this additional properties and form > a correct json response. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1437) Add additional properties to OData Server Error
Ramya created OLINGO-1437: - Summary: Add additional properties to OData Server Error Key: OLINGO-1437 URL: https://issues.apache.org/jira/browse/OLINGO-1437 Project: Olingo Issue Type: New Feature Reporter: Ramya Assignee: Ramya OData error response can contain some additional fields: @Common.longtextUrl @Common.numericSeverity (only within details section) @Common.additionalTargets Olingo does not provide a way to specify these additional properties in either ODataServerError or ODataErrorDetail. Implementation detail: Add an API setAdditionalProperties and getAdditionalProperties in ODataServerError and ODataErrorDetail which allows to add these additional properties. The ODataErrorSerializer should serialize this additional properties and form a correct json response. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1062) Cannot consume Odata Reference Services with Annotations
[
https://issues.apache.org/jira/browse/OLINGO-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062283#comment-17062283
]
Ramya commented on OLINGO-1062:
---
Some code improvements as part of the commit
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=d4c057b80c5a185401b7233665f69206bea789b6
> Cannot consume Odata Reference Services with Annotations
>
>
> Key: OLINGO-1062
> URL: https://issues.apache.org/jira/browse/OLINGO-1062
> Project: Olingo
> Issue Type: Bug
> Components: odata4-client
>Affects Versions: (Java) V4 4.3.0
>Reporter: Lars Laegner
>Priority: Major
>
> The http://services.odata.org/TripPinRESTierService/ service returns the
> following annotation:
> ...
> EntityType="Microsoft.OData.Service.Sample.TrippinInMemory.Models.Airline">
>
> Name...
> unfortunately, the used Org.OData.Core.V1 namespace is not referencing
> anywhere an alias or namespace in the schema.
> This results, when retrieving the code with the latest available OData V4 Lib
> for Java, in the EdmAnnotationClass Code
> public EdmTerm getTerm() {
> if (term == null) {
> if (annotation.getTerm() == null) { throw new EdmException("Term must not be
> null for an annotation."); }
> term = edm.getTerm(new FullQualifiedName(annotation.getTerm()));
> }
> return term; }
> that in debugging the
> annotation.getTerm()=="Org.OData.Core.V1.OptimisticConcurrency" but the term
> is then set to null from edm.getTerm() as it seems to check for available
> namespace/aliases in the schema and cannot find one.
> So practically, this annotation does not exist for the currently latest
> Olingo-OData-Client-for-Java-4.3.0
> The same for
> http://services.odata.org/V4/(S(tauqx0n1pg4nytucatnssdwb))/TripPinServiceRW/
> I have cross created this issue in
> https://github.com/OData/odataorg.github.io/issues/117 as i am not sure,
> wether the service is not correct or the client should be more forgiving
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OLINGO-1368) OData V4: Support In Operator in filters
[ https://issues.apache.org/jira/browse/OLINGO-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045169#comment-17045169 ] Ramya commented on OLINGO-1368: --- Bug fix as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=ac7d8dbd62d4b284b580618bfb1cac4bf7831e73 > OData V4: Support In Operator in filters > > > Key: OLINGO-1368 > URL: https://issues.apache.org/jira/browse/OLINGO-1368 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Priority: Major > > Add support for In operator as per the specification > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OLINGO-1388) OData V2: Allow Content-id referencing across changesets
[ https://issues.apache.org/jira/browse/OLINGO-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1388. - > OData V2: Allow Content-id referencing across changesets > > > Key: OLINGO-1388 > URL: https://issues.apache.org/jira/browse/OLINGO-1388 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Currently in V2 we do not allow content-id referencing across changesets. > Now content-id referenced must be unique for the entire batch request > Sample batch payload > --batch_005056A5-09B1-1ED1-BF82-409B26A80300 > Content-Type: multipart/mixed; > boundary=changeset_005056A5-09B1-1ED1-BF82-409B26A80301 > --changeset_005056A5-09B1-1ED1-BF82-409B26A80301 > Content-Type: application/http > Content-Transfer-Encoding: binary > POST Rooms HTTP/1.1 > Content-Type: application/atom+xml > Content-ID: 2 > http://www.w3.org/2005/Atom; > xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata; > xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices;> > > > > Room 1 > 1 > 1 > > > > -changeset_005056A5-09B1-1ED1-BF82-409B26A80301- > --batch_005056A5-09B1-1ED1-BF82-409B26A80300 > Content-Type: application/http > Content-Transfer-Encoding: binary > GET $2/nr_Building HTTP/1.1 > -batch_005056A5-09B1-1ED1-BF82-409B26A80300- -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OLINGO-1375) OData V4: EntitySet in function Import need not be prefixed with namespace
[ https://issues.apache.org/jira/browse/OLINGO-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1375. - > OData V4: EntitySet in function Import need not be prefixed with namespace > -- > > Key: OLINGO-1375 > URL: https://issues.apache.org/jira/browse/OLINGO-1375 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Assignee: Ramya >Priority: Minor > > If EntitySet specified in function Import is within the same container as the > function import then no need to prefix it with namespace -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OLINGO-1391) OData V4: Move the olingo library to java 8
[ https://issues.apache.org/jira/browse/OLINGO-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1391. - > OData V4: Move the olingo library to java 8 > --- > > Key: OLINGO-1391 > URL: https://issues.apache.org/jira/browse/OLINGO-1391 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Change the jdk version to 1.8. Henceforth compile olingo libraries with java > 8. > This will help us leverage the new features available on java 8. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OLINGO-1429) OData V4: Enhance metadata serializer to include Entity Set attribute for an Action Import
[ https://issues.apache.org/jira/browse/OLINGO-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1429. - > OData V4: Enhance metadata serializer to include Entity Set attribute for an > Action Import > -- > > Key: OLINGO-1429 > URL: https://issues.apache.org/jira/browse/OLINGO-1429 > Project: Olingo > Issue Type: Improvement >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per odata v4.01 specification an Action import may include EntitySet > attribute if the action returns an Entity or collection of entities. > http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#_Toc31805584 > Currently the serializer completely ignores the Entity Set attribute. > The fix has to be done in MetadataDocumentXmlSerializer.java -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1421) Handling incorrect message in UriHelperImpl
[ https://issues.apache.org/jira/browse/OLINGO-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1421. --- Resolution: Fixed > Handling incorrect message in UriHelperImpl > --- > > Key: OLINGO-1421 > URL: https://issues.apache.org/jira/browse/OLINGO-1421 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Reporter: Ramya >Assignee: Ramya >Priority: Major > > In UriHelperImpl class, when property is null, an exception is thrown. There > is only 1 argument passed to the Message Key. However, the actual error > message is expecting 2 arguments which is throwing the exception > Missing replacement for place holder in message 'The value '%2$s' is not > valid for property '%1$s'.' for following arguments '[ID] > Error at > at > org.apache.olingo.server.core.uri.UriHelperImpl.findPropertyRefValue(UriHelperImpl.java:127) > ~[odata-v4-lib-1.2.0-20200114.114227-90.jar:?] > at > org.apache.olingo.server.core.uri.UriHelperImpl.buildKeyPredicate(UriHelperImpl.java:88) > ~[odata-v4-lib-1.2.0-20200114.114227-90.jar:?] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OLINGO-1397) OData V4: Handle post requests when there is no content type and payload
[ https://issues.apache.org/jira/browse/OLINGO-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1397. - > OData V4: Handle post requests when there is no content type and payload > > > Key: OLINGO-1397 > URL: https://issues.apache.org/jira/browse/OLINGO-1397 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Assignee: Ramya >Priority: Major > > We should set the content type to default value of application/json, when > user does not send Content-Type header for POST requests. User usually does > not send Content-Type header when he does not send payload i.e payload is > either empty or null -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OLINGO-1393) OData V4.01: Validate the values for a Decimal data type as per latest spec
[ https://issues.apache.org/jira/browse/OLINGO-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1393. - > OData V4.01: Validate the values for a Decimal data type as per latest spec > --- > > Key: OLINGO-1393 > URL: https://issues.apache.org/jira/browse/OLINGO-1393 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per the latest spec, the value of scale is the number of values after the > decimal point always. The remaining digits(Precision-Scale) is the number of > digits allowed before the decimal. So 10.5, 123 are all invalid values > https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd05/odata-csdl-xml-v4.01-csprd05.html#sec_Scale > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OLINGO-1431) OData V4: Remove versions in Import-Packages for client-core
[ https://issues.apache.org/jira/browse/OLINGO-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1431. - > OData V4: Remove versions in Import-Packages for client-core > > > Key: OLINGO-1431 > URL: https://issues.apache.org/jira/browse/OLINGO-1431 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Assignee: Ramya >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OLINGO-1430) OData V4: Enhance metadata serializer to include OnDelete child element for a navigation Property
[ https://issues.apache.org/jira/browse/OLINGO-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1430. - > OData V4: Enhance metadata serializer to include OnDelete child element for a > navigation Property > - > > Key: OLINGO-1430 > URL: https://issues.apache.org/jira/browse/OLINGO-1430 > Project: Olingo > Issue Type: Improvement >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per the odata v4.01 specification a navigation property can have OnDelete > child element > http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_OnDeleteAction > Currently the metadata serializer ignores this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1431) OData V4: Remove versions in Import-Packages for client-core
[ https://issues.apache.org/jira/browse/OLINGO-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17040752#comment-17040752 ] Ramya commented on OLINGO-1431: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=ea727e92253ebc3d4a8f08dde635b93d86f71fb0 > OData V4: Remove versions in Import-Packages for client-core > > > Key: OLINGO-1431 > URL: https://issues.apache.org/jira/browse/OLINGO-1431 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Assignee: Ramya >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1431) OData V4: Remove versions in Import-Packages for client-core
[ https://issues.apache.org/jira/browse/OLINGO-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1431. --- Resolution: Fixed > OData V4: Remove versions in Import-Packages for client-core > > > Key: OLINGO-1431 > URL: https://issues.apache.org/jira/browse/OLINGO-1431 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Assignee: Ramya >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1431) OData V4: Remove versions in Import-Packages for client-core
Ramya created OLINGO-1431: - Summary: OData V4: Remove versions in Import-Packages for client-core Key: OLINGO-1431 URL: https://issues.apache.org/jira/browse/OLINGO-1431 Project: Olingo Issue Type: Bug Reporter: Ramya Assignee: Ramya -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1430) OData V4: Enhance metadata serializer to include OnDelete child element for a navigation Property
[ https://issues.apache.org/jira/browse/OLINGO-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1430. --- Resolution: Fixed > OData V4: Enhance metadata serializer to include OnDelete child element for a > navigation Property > - > > Key: OLINGO-1430 > URL: https://issues.apache.org/jira/browse/OLINGO-1430 > Project: Olingo > Issue Type: Improvement >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per the odata v4.01 specification a navigation property can have OnDelete > child element > http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_OnDeleteAction > Currently the metadata serializer ignores this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1430) OData V4: Enhance metadata serializer to include OnDelete child element for a navigation Property
[ https://issues.apache.org/jira/browse/OLINGO-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17040642#comment-17040642 ] Ramya commented on OLINGO-1430: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=acb5e5e74c4ab3a942523786394e087defa9b779 > OData V4: Enhance metadata serializer to include OnDelete child element for a > navigation Property > - > > Key: OLINGO-1430 > URL: https://issues.apache.org/jira/browse/OLINGO-1430 > Project: Olingo > Issue Type: Improvement >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per the odata v4.01 specification a navigation property can have OnDelete > child element > http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_OnDeleteAction > Currently the metadata serializer ignores this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OLINGO-1430) OData V4: Enhance metadata serializer to include OnDelete child element for a navigation Property
[ https://issues.apache.org/jira/browse/OLINGO-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya reassigned OLINGO-1430: - Assignee: Ramya > OData V4: Enhance metadata serializer to include OnDelete child element for a > navigation Property > - > > Key: OLINGO-1430 > URL: https://issues.apache.org/jira/browse/OLINGO-1430 > Project: Olingo > Issue Type: Improvement >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per the odata v4.01 specification a navigation property can have OnDelete > child element > http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_OnDeleteAction > Currently the metadata serializer ignores this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1430) OData V4: Enhance metadata serializer to include OnDelete child element for a navigation Property
Ramya created OLINGO-1430: - Summary: OData V4: Enhance metadata serializer to include OnDelete child element for a navigation Property Key: OLINGO-1430 URL: https://issues.apache.org/jira/browse/OLINGO-1430 Project: Olingo Issue Type: Improvement Reporter: Ramya As per the odata v4.01 specification a navigation property can have OnDelete child element http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_OnDeleteAction Currently the metadata serializer ignores this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1429) OData V4: Enhance metadata serializer to include Entity Set attribute for an Action Import
[ https://issues.apache.org/jira/browse/OLINGO-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17040621#comment-17040621 ] Ramya commented on OLINGO-1429: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=5b790f82c70f00d418dda1a0697d9a6e3a949fe7 > OData V4: Enhance metadata serializer to include Entity Set attribute for an > Action Import > -- > > Key: OLINGO-1429 > URL: https://issues.apache.org/jira/browse/OLINGO-1429 > Project: Olingo > Issue Type: Improvement >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per odata v4.01 specification an Action import may include EntitySet > attribute if the action returns an Entity or collection of entities. > http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#_Toc31805584 > Currently the serializer completely ignores the Entity Set attribute. > The fix has to be done in MetadataDocumentXmlSerializer.java -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1429) OData V4: Enhance metadata serializer to include Entity Set attribute for an Action Import
[ https://issues.apache.org/jira/browse/OLINGO-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1429. --- Resolution: Fixed > OData V4: Enhance metadata serializer to include Entity Set attribute for an > Action Import > -- > > Key: OLINGO-1429 > URL: https://issues.apache.org/jira/browse/OLINGO-1429 > Project: Olingo > Issue Type: Improvement >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per odata v4.01 specification an Action import may include EntitySet > attribute if the action returns an Entity or collection of entities. > http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#_Toc31805584 > Currently the serializer completely ignores the Entity Set attribute. > The fix has to be done in MetadataDocumentXmlSerializer.java -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1429) OData V4: Enhance metadata serializer to include Entity Set attribute for an Action Import
Ramya created OLINGO-1429: - Summary: OData V4: Enhance metadata serializer to include Entity Set attribute for an Action Import Key: OLINGO-1429 URL: https://issues.apache.org/jira/browse/OLINGO-1429 Project: Olingo Issue Type: Improvement Reporter: Ramya Assignee: Ramya As per odata v4.01 specification an Action import may include EntitySet attribute if the action returns an Entity or collection of entities. http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#_Toc31805584 Currently the serializer completely ignores the Entity Set attribute. The fix has to be done in MetadataDocumentXmlSerializer.java -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1238) OData V4: Code Improvements in handling exceptions
[ https://issues.apache.org/jira/browse/OLINGO-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17040613#comment-17040613 ] Ramya commented on OLINGO-1238: --- A small code improvement as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=a7f98f8842856319809db32b16c88354993b4178 > OData V4: Code Improvements in handling exceptions > -- > > Key: OLINGO-1238 > URL: https://issues.apache.org/jira/browse/OLINGO-1238 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Ramya >Priority: Major > > When the OData-Version header is specified less than 4.0 then we throw 400 > Bad Request error and when the value is greater than 4.01 we throw 400 Bad > Request error > When the OData-MaxVersion header is specified less than 4.0 then we throw 400 > Bad Request error and when the value is greater than 4.01 the request is > processed. > When the Accept header has a charset which violates ABNF, we throw 400 Bad > Request and if it is as per ABNF but wrong format like application/abc, then > we throw 406 Not Acceptable. > When the Accept charset header has a charset which violates ABNF, we throw > 400 Bad Request and if it is as per ABNF but other than utf-8, then we throw > 406 Not Acceptable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1421) Handling incorrect message in UriHelperImpl
[ https://issues.apache.org/jira/browse/OLINGO-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016486#comment-17016486 ] Ramya commented on OLINGO-1421: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=a1dfb5596b4266f30ae503d3d3e116f269561640 > Handling incorrect message in UriHelperImpl > --- > > Key: OLINGO-1421 > URL: https://issues.apache.org/jira/browse/OLINGO-1421 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Reporter: Ramya >Assignee: Ramya >Priority: Major > > In UriHelperImpl class, when property is null, an exception is thrown. There > is only 1 argument passed to the Message Key. However, the actual error > message is expecting 2 arguments which is throwing the exception > Missing replacement for place holder in message 'The value '%2$s' is not > valid for property '%1$s'.' for following arguments '[ID] > Error at > at > org.apache.olingo.server.core.uri.UriHelperImpl.findPropertyRefValue(UriHelperImpl.java:127) > ~[odata-v4-lib-1.2.0-20200114.114227-90.jar:?] > at > org.apache.olingo.server.core.uri.UriHelperImpl.buildKeyPredicate(UriHelperImpl.java:88) > ~[odata-v4-lib-1.2.0-20200114.114227-90.jar:?] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1421) Handling incorrect message in UriHelperImpl
Ramya created OLINGO-1421: - Summary: Handling incorrect message in UriHelperImpl Key: OLINGO-1421 URL: https://issues.apache.org/jira/browse/OLINGO-1421 Project: Olingo Issue Type: Bug Components: odata4-server Reporter: Ramya Assignee: Ramya In UriHelperImpl class, when property is null, an exception is thrown. There is only 1 argument passed to the Message Key. However, the actual error message is expecting 2 arguments which is throwing the exception Missing replacement for place holder in message 'The value '%2$s' is not valid for property '%1$s'.' for following arguments '[ID] Error at at org.apache.olingo.server.core.uri.UriHelperImpl.findPropertyRefValue(UriHelperImpl.java:127) ~[odata-v4-lib-1.2.0-20200114.114227-90.jar:?] at org.apache.olingo.server.core.uri.UriHelperImpl.buildKeyPredicate(UriHelperImpl.java:88) ~[odata-v4-lib-1.2.0-20200114.114227-90.jar:?] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1417) OData V4: Adopt search option based on new V4 abnf
[ https://issues.apache.org/jira/browse/OLINGO-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014956#comment-17014956 ] Ramya commented on OLINGO-1417: --- Few more changes as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=1df2f4aa67e9ed5c3cc10f3abc65f9e1fd7ee042 > OData V4: Adopt search option based on new V4 abnf > --- > > Key: OLINGO-1417 > URL: https://issues.apache.org/jira/browse/OLINGO-1417 > Project: Olingo > Issue Type: Improvement > Components: odata4-server >Reporter: Ramya >Priority: Major > Fix For: (Java) V4 4.7.1 > > > The ABNF for V4 was overly restrictive for search system query option, this > got fixed lated in > https://github.com/oasis-tcs/odata-abnf/blob/master/abnf/odata-abnf-construction-rules.txt#L332-L356. > Numbers are fine, as are numbers with decimal point or decimal comma, minus > signs, and any percent-encoded Unicode character from categories Letter (L) > and Number (N). > The library should be enhanced to support this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1417) OData V4: Adopt search option based on new V4 abnf
[ https://issues.apache.org/jira/browse/OLINGO-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1417. --- Resolution: Fixed > OData V4: Adopt search option based on new V4 abnf > --- > > Key: OLINGO-1417 > URL: https://issues.apache.org/jira/browse/OLINGO-1417 > Project: Olingo > Issue Type: Improvement > Components: odata4-server >Reporter: Ramya >Priority: Major > > The ABNF for V4 was overly restrictive for search system query option, this > got fixed lated in > https://github.com/oasis-tcs/odata-abnf/blob/master/abnf/odata-abnf-construction-rules.txt#L332-L356. > Numbers are fine, as are numbers with decimal point or decimal comma, minus > signs, and any percent-encoded Unicode character from categories Letter (L) > and Number (N). > The library should be enhanced to support this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1417) OData V4: Adopt search option based on new V4 abnf
[ https://issues.apache.org/jira/browse/OLINGO-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998818#comment-16998818 ] Ramya commented on OLINGO-1417: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=dfe1dd288c4f706a91b59a620f30c0c60b2ce1d7 > OData V4: Adopt search option based on new V4 abnf > --- > > Key: OLINGO-1417 > URL: https://issues.apache.org/jira/browse/OLINGO-1417 > Project: Olingo > Issue Type: Improvement > Components: odata4-server >Reporter: Ramya >Priority: Major > > The ABNF for V4 was overly restrictive for search system query option, this > got fixed lated in > https://github.com/oasis-tcs/odata-abnf/blob/master/abnf/odata-abnf-construction-rules.txt#L332-L356. > Numbers are fine, as are numbers with decimal point or decimal comma, minus > signs, and any percent-encoded Unicode character from categories Letter (L) > and Number (N). > The library should be enhanced to support this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1417) OData V4: Adopt search option based on new V4 abnf
Ramya created OLINGO-1417: - Summary: OData V4: Adopt search option based on new V4 abnf Key: OLINGO-1417 URL: https://issues.apache.org/jira/browse/OLINGO-1417 Project: Olingo Issue Type: Improvement Components: odata4-server Reporter: Ramya The ABNF for V4 was overly restrictive for search system query option, this got fixed lated in https://github.com/oasis-tcs/odata-abnf/blob/master/abnf/odata-abnf-construction-rules.txt#L332-L356. Numbers are fine, as are numbers with decimal point or decimal comma, minus signs, and any percent-encoded Unicode character from categories Letter (L) and Number (N). The library should be enhanced to support this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1176) OData V2.0: Code Improvements
[ https://issues.apache.org/jira/browse/OLINGO-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16958534#comment-16958534 ] Ramya commented on OLINGO-1176: --- A small improvement in error handling is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=2c5a87ab54f448cfff167d95821065b529ac8952 > OData V2.0: Code Improvements > - > > Key: OLINGO-1176 > URL: https://issues.apache.org/jira/browse/OLINGO-1176 > Project: Olingo > Issue Type: Bug >Affects Versions: V2 2.0.9 >Reporter: Ramya >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OLINGO-1391) OData V4: Move the olingo library to java 8
[ https://issues.apache.org/jira/browse/OLINGO-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929053#comment-16929053 ] Ramya commented on OLINGO-1391: --- More code improvements as part of commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=6c2103ccd4fce21b1270bad52c72c01627d39ea4 > OData V4: Move the olingo library to java 8 > --- > > Key: OLINGO-1391 > URL: https://issues.apache.org/jira/browse/OLINGO-1391 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Change the jdk version to 1.8. Henceforth compile olingo libraries with java > 8. > This will help us leverage the new features available on java 8. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OLINGO-1155) Delta support in Json format
[ https://issues.apache.org/jira/browse/OLINGO-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929022#comment-16929022 ] Ramya commented on OLINGO-1155: --- Bug fix in nextLink as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=8f4d03195786968830111e8cf41614c05d02c99b > Delta support in Json format > > > Key: OLINGO-1155 > URL: https://issues.apache.org/jira/browse/OLINGO-1155 > Project: Olingo > Issue Type: New Feature > Components: odata4-server >Reporter: Archana Rai >Priority: Major > > Currently the olingo from the server side do not support Delta feature. > The response is different in version 4 and 4.01. Hence both should be > supported. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OLINGO-1397) OData V4: Handle post requests when there is no content type and payload
[ https://issues.apache.org/jira/browse/OLINGO-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929014#comment-16929014 ] Ramya commented on OLINGO-1397: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=b5be47209786d509c2f48f34013d0b5a5f1937a1 > OData V4: Handle post requests when there is no content type and payload > > > Key: OLINGO-1397 > URL: https://issues.apache.org/jira/browse/OLINGO-1397 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Assignee: Ramya >Priority: Major > > We should set the content type to default value of application/json, when > user does not send Content-Type header for POST requests. User usually does > not send Content-Type header when he does not send payload i.e payload is > either empty or null -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (OLINGO-1397) OData V4: Handle post requests when there is no content type and payload
[ https://issues.apache.org/jira/browse/OLINGO-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1397. --- Resolution: Fixed > OData V4: Handle post requests when there is no content type and payload > > > Key: OLINGO-1397 > URL: https://issues.apache.org/jira/browse/OLINGO-1397 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Assignee: Ramya >Priority: Major > > We should set the content type to default value of application/json, when > user does not send Content-Type header for POST requests. User usually does > not send Content-Type header when he does not send payload i.e payload is > either empty or null -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (OLINGO-1397) OData V4: Handle post requests when there is no content type and payload
Ramya created OLINGO-1397: - Summary: OData V4: Handle post requests when there is no content type and payload Key: OLINGO-1397 URL: https://issues.apache.org/jira/browse/OLINGO-1397 Project: Olingo Issue Type: Bug Reporter: Ramya Assignee: Ramya We should set the content type to default value of application/json, when user does not send Content-Type header for POST requests. User usually does not send Content-Type header when he does not send payload i.e payload is either empty or null -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OLINGO-1391) OData V4: Move the olingo library to java 8
[ https://issues.apache.org/jira/browse/OLINGO-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928417#comment-16928417 ] Ramya commented on OLINGO-1391: --- Code improvements as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=7049f4ebf0021b7f13b6b9c46a334438bc3caa46 > OData V4: Move the olingo library to java 8 > --- > > Key: OLINGO-1391 > URL: https://issues.apache.org/jira/browse/OLINGO-1391 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Change the jdk version to 1.8. Henceforth compile olingo libraries with java > 8. > This will help us leverage the new features available on java 8. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OLINGO-1368) OData V4: Support In Operator in filters
[ https://issues.apache.org/jira/browse/OLINGO-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928326#comment-16928326 ] Ramya commented on OLINGO-1368: --- Bug Fix as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=7f3f9c5261d6c82b87b753510bab950ebc237157 > OData V4: Support In Operator in filters > > > Key: OLINGO-1368 > URL: https://issues.apache.org/jira/browse/OLINGO-1368 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Priority: Major > > Add support for In operator as per the specification > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OLINGO-1155) Delta support in Json format
[ https://issues.apache.org/jira/browse/OLINGO-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925406#comment-16925406 ] Ramya commented on OLINGO-1155: --- Code Improvements as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=21d874d255e14af6837b8530036e06207c8321ba > Delta support in Json format > > > Key: OLINGO-1155 > URL: https://issues.apache.org/jira/browse/OLINGO-1155 > Project: Olingo > Issue Type: New Feature > Components: odata4-server >Reporter: Archana Rai >Priority: Major > > Currently the olingo from the server side do not support Delta feature. > The response is different in version 4 and 4.01. Hence both should be > supported. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OLINGO-1393) OData V4.01: Validate the values for a Decimal data type as per latest spec
[ https://issues.apache.org/jira/browse/OLINGO-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925379#comment-16925379 ] Ramya commented on OLINGO-1393: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=510b213cd6b505aed7edd3febfbb058e48bcc4e9 > OData V4.01: Validate the values for a Decimal data type as per latest spec > --- > > Key: OLINGO-1393 > URL: https://issues.apache.org/jira/browse/OLINGO-1393 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per the latest spec, the value of scale is the number of values after the > decimal point always. The remaining digits(Precision-Scale) is the number of > digits allowed before the decimal. So 10.5, 123 are all invalid values > https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd05/odata-csdl-xml-v4.01-csprd05.html#sec_Scale > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (OLINGO-1393) OData V4.01: Validate the values for a Decimal data type as per latest spec
[ https://issues.apache.org/jira/browse/OLINGO-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1393. --- Resolution: Fixed > OData V4.01: Validate the values for a Decimal data type as per latest spec > --- > > Key: OLINGO-1393 > URL: https://issues.apache.org/jira/browse/OLINGO-1393 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > As per the latest spec, the value of scale is the number of values after the > decimal point always. The remaining digits(Precision-Scale) is the number of > digits allowed before the decimal. So 10.5, 123 are all invalid values > https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd05/odata-csdl-xml-v4.01-csprd05.html#sec_Scale > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (OLINGO-1393) OData V4.01: Validate the values for a Decimal data type as per latest spec
Ramya created OLINGO-1393: - Summary: OData V4.01: Validate the values for a Decimal data type as per latest spec Key: OLINGO-1393 URL: https://issues.apache.org/jira/browse/OLINGO-1393 Project: Olingo Issue Type: New Feature Reporter: Ramya Assignee: Ramya As per the latest spec, the value of scale is the number of values after the decimal point always. The remaining digits(Precision-Scale) is the number of digits allowed before the decimal. So 10.5, 123 are all invalid values https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd05/odata-csdl-xml-v4.01-csprd05.html#sec_Scale -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OLINGO-1391) OData V4: Move the olingo library to java 8
[ https://issues.apache.org/jira/browse/OLINGO-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925363#comment-16925363 ] Ramya commented on OLINGO-1391: --- Merged as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=9f8cbc6fcc38b3031c2765ce1952e1e4b5767451 > OData V4: Move the olingo library to java 8 > --- > > Key: OLINGO-1391 > URL: https://issues.apache.org/jira/browse/OLINGO-1391 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Change the jdk version to 1.8. Henceforth compile olingo libraries with java > 8. > This will help us leverage the new features available on java 8. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (OLINGO-1391) OData V4: Move the olingo library to java 8
[ https://issues.apache.org/jira/browse/OLINGO-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1391. --- Resolution: Fixed > OData V4: Move the olingo library to java 8 > --- > > Key: OLINGO-1391 > URL: https://issues.apache.org/jira/browse/OLINGO-1391 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Change the jdk version to 1.8. Henceforth compile olingo libraries with java > 8. > This will help us leverage the new features available on java 8. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (OLINGO-1391) OData V4: Move the olingo library to java 8
Ramya created OLINGO-1391: - Summary: OData V4: Move the olingo library to java 8 Key: OLINGO-1391 URL: https://issues.apache.org/jira/browse/OLINGO-1391 Project: Olingo Issue Type: New Feature Reporter: Ramya Assignee: Ramya Change the jdk version to 1.8. Henceforth compile olingo libraries with java 8. This will help us leverage the new features available on java 8. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OLINGO-1155) Delta support in Json format
[ https://issues.apache.org/jira/browse/OLINGO-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918274#comment-16918274 ] Ramya commented on OLINGO-1155: --- Handling empty navigation property and handling full representation of delta: https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=7632ec726845345467d07800e56723c30a053a3b Thanks Ramya > Delta support in Json format > > > Key: OLINGO-1155 > URL: https://issues.apache.org/jira/browse/OLINGO-1155 > Project: Olingo > Issue Type: New Feature > Components: odata4-server >Reporter: Archana Rai >Priority: Major > > Currently the olingo from the server side do not support Delta feature. > The response is different in version 4 and 4.01. Hence both should be > supported. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OLINGO-1054) Inline Consumer Callback Data handling
[ https://issues.apache.org/jira/browse/OLINGO-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917384#comment-16917384 ] Ramya commented on OLINGO-1054: --- Handling when metadata is null with this commit : https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=e8ec21c40efe29c9ac0aaee507e905ff69dc249c > Inline Consumer Callback Data handling > -- > > Key: OLINGO-1054 > URL: https://issues.apache.org/jira/browse/OLINGO-1054 > Project: Olingo > Issue Type: New Feature > Components: odata2-core >Affects Versions: V2 2.0.6, V2 2.0.7 >Reporter: Ramya >Assignee: Christian Amend >Priority: Major > Fix For: V2 2.0.9 > > Attachments: 626b49ed.diff > > > When using the consumer callbacks the data is not part of the result. Yet > since there is no access to the parent data the callback can`t decide where > to put the data. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (OLINGO-1388) OData V2: Allow Content-id referencing across changesets
[ https://issues.apache.org/jira/browse/OLINGO-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1388. --- Resolution: Fixed > OData V2: Allow Content-id referencing across changesets > > > Key: OLINGO-1388 > URL: https://issues.apache.org/jira/browse/OLINGO-1388 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Currently in V2 we do not allow content-id referencing across changesets. > Now content-id referenced must be unique for the entire batch request > Sample batch payload > --batch_005056A5-09B1-1ED1-BF82-409B26A80300 > Content-Type: multipart/mixed; > boundary=changeset_005056A5-09B1-1ED1-BF82-409B26A80301 > --changeset_005056A5-09B1-1ED1-BF82-409B26A80301 > Content-Type: application/http > Content-Transfer-Encoding: binary > POST Rooms HTTP/1.1 > Content-Type: application/atom+xml > Content-ID: 2 > http://www.w3.org/2005/Atom; > xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata; > xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices;> > > > > Room 1 > 1 > 1 > > > > -changeset_005056A5-09B1-1ED1-BF82-409B26A80301- > --batch_005056A5-09B1-1ED1-BF82-409B26A80300 > Content-Type: application/http > Content-Transfer-Encoding: binary > GET $2/nr_Building HTTP/1.1 > -batch_005056A5-09B1-1ED1-BF82-409B26A80300- -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OLINGO-1388) OData V2: Allow Content-id referencing across changesets
[ https://issues.apache.org/jira/browse/OLINGO-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917377#comment-16917377 ] Ramya commented on OLINGO-1388: --- This is supported as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=9631139c22564ce0a549a727ca673eab40f4c9e6 > OData V2: Allow Content-id referencing across changesets > > > Key: OLINGO-1388 > URL: https://issues.apache.org/jira/browse/OLINGO-1388 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Currently in V2 we do not allow content-id referencing across changesets. > Now content-id referenced must be unique for the entire batch request > Sample batch payload > --batch_005056A5-09B1-1ED1-BF82-409B26A80300 > Content-Type: multipart/mixed; > boundary=changeset_005056A5-09B1-1ED1-BF82-409B26A80301 > --changeset_005056A5-09B1-1ED1-BF82-409B26A80301 > Content-Type: application/http > Content-Transfer-Encoding: binary > POST Rooms HTTP/1.1 > Content-Type: application/atom+xml > Content-ID: 2 > http://www.w3.org/2005/Atom; > xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata; > xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices;> > > > > Room 1 > 1 > 1 > > > > -changeset_005056A5-09B1-1ED1-BF82-409B26A80301- > --batch_005056A5-09B1-1ED1-BF82-409B26A80300 > Content-Type: application/http > Content-Transfer-Encoding: binary > GET $2/nr_Building HTTP/1.1 > -batch_005056A5-09B1-1ED1-BF82-409B26A80300- -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (OLINGO-1203) Locale information is not set to error context
[ https://issues.apache.org/jira/browse/OLINGO-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1203. - Assignee: Ramya > Locale information is not set to error context > -- > > Key: OLINGO-1203 > URL: https://issues.apache.org/jira/browse/OLINGO-1203 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.8, V2 2.0.9 >Reporter: Ramya >Assignee: Ramya >Priority: Minor > > Locale information is not set to odata error context when ODataApplication > Exception is thrown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (OLINGO-1362) OData V2: Missed http status code 420
[ https://issues.apache.org/jira/browse/OLINGO-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1362. - Assignee: Ramya > OData V2: Missed http status code 420 > - > > Key: OLINGO-1362 > URL: https://issues.apache.org/jira/browse/OLINGO-1362 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.11 >Reporter: Ramya >Assignee: Ramya >Priority: Major > > Http status code 420 is not listed in > org/apache/olingo/odata2/api/commons/HttpStatusCodes.java > 420 http status code is a deprecated response and also it used to be the > return code for Twitter Search and Trends API when the client is being rate > limited. This 420 status code is not added in the olingo HttpStatusCodes and > hence the applications get 500 Internal server error. > (https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (OLINGO-1375) OData V4: EntitySet in function Import need not be prefixed with namespace
[ https://issues.apache.org/jira/browse/OLINGO-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1375. --- Assignee: Ramya Resolution: Fixed > OData V4: EntitySet in function Import need not be prefixed with namespace > -- > > Key: OLINGO-1375 > URL: https://issues.apache.org/jira/browse/OLINGO-1375 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Assignee: Ramya >Priority: Minor > > If EntitySet specified in function Import is within the same container as the > function import then no need to prefix it with namespace -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (OLINGO-1380) OData V4: Response header information is lost in case of exceptions
[ https://issues.apache.org/jira/browse/OLINGO-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya closed OLINGO-1380. - > OData V4: Response header information is lost in case of exceptions > --- > > Key: OLINGO-1380 > URL: https://issues.apache.org/jira/browse/OLINGO-1380 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Priority: Major > > Whenever an exception occurs in client scenarios we throw > ODataClientErrorException with statusLine and ODataError. However, the > response header information is lost. > So have new API's in ODataClientErrorException to set and get header > information. > Also, currently if the response is in a Json format only then we can > deserialize the entity and form ODataError. > If the server returns the response as a plain text, then also make provision > to include this information in ODataError object. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (OLINGO-1388) OData V2: Allow Content-id referencing across changesets
Ramya created OLINGO-1388: - Summary: OData V2: Allow Content-id referencing across changesets Key: OLINGO-1388 URL: https://issues.apache.org/jira/browse/OLINGO-1388 Project: Olingo Issue Type: Bug Components: odata2-core Reporter: Ramya Assignee: Ramya Currently in V2 we do not allow content-id referencing across changesets. Now content-id referenced must be unique for the entire batch request Sample batch payload --batch_005056A5-09B1-1ED1-BF82-409B26A80300 Content-Type: multipart/mixed; boundary=changeset_005056A5-09B1-1ED1-BF82-409B26A80301 --changeset_005056A5-09B1-1ED1-BF82-409B26A80301 Content-Type: application/http Content-Transfer-Encoding: binary POST Rooms HTTP/1.1 Content-Type: application/atom+xml Content-ID: 2 http://www.w3.org/2005/Atom; xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata; xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices;> Room 1 1 1 -changeset_005056A5-09B1-1ED1-BF82-409B26A80301- --batch_005056A5-09B1-1ED1-BF82-409B26A80300 Content-Type: application/http Content-Transfer-Encoding: binary GET $2/nr_Building HTTP/1.1 -batch_005056A5-09B1-1ED1-BF82-409B26A80300- -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (OLINGO-1380) OData V4: Response header information is lost in case of exceptions
[ https://issues.apache.org/jira/browse/OLINGO-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1380. --- Resolution: Fixed > OData V4: Response header information is lost in case of exceptions > --- > > Key: OLINGO-1380 > URL: https://issues.apache.org/jira/browse/OLINGO-1380 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Priority: Major > > Whenever an exception occurs in client scenarios we throw > ODataClientErrorException with statusLine and ODataError. However, the > response header information is lost. > So have new API's in ODataClientErrorException to set and get header > information. > Also, currently if the response is in a Json format only then we can > deserialize the entity and form ODataError. > If the server returns the response as a plain text, then also make provision > to include this information in ODataError object. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (OLINGO-1380) OData V4: Response header information is lost in case of exceptions
[ https://issues.apache.org/jira/browse/OLINGO-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898636#comment-16898636 ] Ramya commented on OLINGO-1380: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=e3650599007a917890963fbec6a19b437d519e4d > OData V4: Response header information is lost in case of exceptions > --- > > Key: OLINGO-1380 > URL: https://issues.apache.org/jira/browse/OLINGO-1380 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Priority: Major > > Whenever an exception occurs in client scenarios we throw > ODataClientErrorException with statusLine and ODataError. However, the > response header information is lost. > So have new API's in ODataClientErrorException to set and get header > information. > Also, currently if the response is in a Json format only then we can > deserialize the entity and form ODataError. > If the server returns the response as a plain text, then also make provision > to include this information in ODataError object. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (OLINGO-1380) OData V4: Response header information is lost in case of exceptions
Ramya created OLINGO-1380: - Summary: OData V4: Response header information is lost in case of exceptions Key: OLINGO-1380 URL: https://issues.apache.org/jira/browse/OLINGO-1380 Project: Olingo Issue Type: Bug Reporter: Ramya Whenever an exception occurs in client scenarios we throw ODataClientErrorException with statusLine and ODataError. However, the response header information is lost. So have new API's in ODataClientErrorException to set and get header information. Also, currently if the response is in a Json format only then we can deserialize the entity and form ODataError. If the server returns the response as a plain text, then also make provision to include this information in ODataError object. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (OLINGO-1228) JPA Parameterization issue
[ https://issues.apache.org/jira/browse/OLINGO-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898574#comment-16898574 ] Ramya commented on OLINGO-1228: --- Small fix as part of commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=ce414cc7ae44eae7aa4f8ffd4f4b124679d7623f > JPA Parameterization issue > --- > > Key: OLINGO-1228 > URL: https://issues.apache.org/jira/browse/OLINGO-1228 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Reporter: Archana Rai >Priority: Major > > Put request with two parameters failing for JPA > [http://localhost:8081/RFQ/Appointments(RequestForQuotationGuid='7f260ade-65e0-471a-b2ce-75e1b745bd54',AppointmentId=3)] > With the below exception: > java.lang.IllegalArgumentException:An exception occurred while > creating a query in EntityManager: > Exception Description: Error compiling the query [SELECT E1 FROM Appointment > E1 WHERE E1.requestForQuotationGuid LIKE ?1 ESCAPE '\' AND E1.appointmentId = > ?1], line 1, column 105: invalid multiple use of parameter [1] assuming > different parameter types [java.lang.String] and [java.lang.Integer] > Parameter 1 in SQL is also used for the second value. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (OLINGO-1367) OData V2: Issue with EdmTime
[ https://issues.apache.org/jira/browse/OLINGO-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882704#comment-16882704 ] Ramya commented on OLINGO-1367: --- Another small fix https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=6f2083a5af1bd24b21479cf4a15d3bcd22041d00 > OData V2: Issue with EdmTime > > > Key: OLINGO-1367 > URL: https://issues.apache.org/jira/browse/OLINGO-1367 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Priority: Major > > As per the specification > https://www.odata.org/documentation/odata-version-2-0/overview/ Edm Time > should be defined by the lexical representation for dayTimeDuration in > http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration. > Currently if user provides time value like P00DT18H03M08S, we get an error >"Caused by: > org.apache.olingo.odata2.api.ep.EntityProviderException: An exception of type > 'EdmSimpleTypeException' occurred.", >"\t... 107 more", >"Caused by: > org.apache.olingo.odata2.api.edm.EdmSimpleTypeException: The literal > 'P00DT18H03M08S' is not formatted properly.", > "\tat > org.apache.olingo.odata2.core.edm.EdmTime.internalValueOfString(EdmTime.java:71)", -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (OLINGO-1375) OData V4: EntitySet in function Import need not be prefixed with namespace
[ https://issues.apache.org/jira/browse/OLINGO-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873927#comment-16873927 ] Ramya commented on OLINGO-1375: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=405fb760886c5c21166981e0469082b191e98fec > OData V4: EntitySet in function Import need not be prefixed with namespace > -- > > Key: OLINGO-1375 > URL: https://issues.apache.org/jira/browse/OLINGO-1375 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Priority: Minor > > If EntitySet specified in function Import is within the same container as the > function import then no need to prefix it with namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OLINGO-1375) OData V4: EntitySet in function Import need not be prefixed with namespace
Ramya created OLINGO-1375: - Summary: OData V4: EntitySet in function Import need not be prefixed with namespace Key: OLINGO-1375 URL: https://issues.apache.org/jira/browse/OLINGO-1375 Project: Olingo Issue Type: Bug Reporter: Ramya If EntitySet specified in function Import is within the same container as the function import then no need to prefix it with namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1368) OData V4: Support In Operator in filters
[ https://issues.apache.org/jira/browse/OLINGO-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865446#comment-16865446 ] Ramya commented on OLINGO-1368: --- This is added as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=aca474ff646e15c1a8332084cdb548c91ecda0b6 > OData V4: Support In Operator in filters > > > Key: OLINGO-1368 > URL: https://issues.apache.org/jira/browse/OLINGO-1368 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Priority: Major > > Add support for In operator as per the specification > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1368) OData V4: Support In Operator in filters
[ https://issues.apache.org/jira/browse/OLINGO-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1368. --- Resolution: Fixed > OData V4: Support In Operator in filters > > > Key: OLINGO-1368 > URL: https://issues.apache.org/jira/browse/OLINGO-1368 > Project: Olingo > Issue Type: New Feature >Reporter: Ramya >Priority: Major > > Add support for In operator as per the specification > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OLINGO-1368) OData V4: Support In Operator in filters
Ramya created OLINGO-1368: - Summary: OData V4: Support In Operator in filters Key: OLINGO-1368 URL: https://issues.apache.org/jira/browse/OLINGO-1368 Project: Olingo Issue Type: New Feature Reporter: Ramya Add support for In operator as per the specification http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1367) OData V2: Issue with EdmTime
[ https://issues.apache.org/jira/browse/OLINGO-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865353#comment-16865353 ] Ramya commented on OLINGO-1367: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=ea8ea9107d9b1177a1ff87fb5ed82e5f40d4e9be > OData V2: Issue with EdmTime > > > Key: OLINGO-1367 > URL: https://issues.apache.org/jira/browse/OLINGO-1367 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Priority: Major > > As per the specification > https://www.odata.org/documentation/odata-version-2-0/overview/ Edm Time > should be defined by the lexical representation for dayTimeDuration in > http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration. > Currently if user provides time value like P00DT18H03M08S, we get an error >"Caused by: > org.apache.olingo.odata2.api.ep.EntityProviderException: An exception of type > 'EdmSimpleTypeException' occurred.", >"\t... 107 more", >"Caused by: > org.apache.olingo.odata2.api.edm.EdmSimpleTypeException: The literal > 'P00DT18H03M08S' is not formatted properly.", > "\tat > org.apache.olingo.odata2.core.edm.EdmTime.internalValueOfString(EdmTime.java:71)", -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1367) OData V2: Issue with EdmTime
[ https://issues.apache.org/jira/browse/OLINGO-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1367. --- Resolution: Fixed > OData V2: Issue with EdmTime > > > Key: OLINGO-1367 > URL: https://issues.apache.org/jira/browse/OLINGO-1367 > Project: Olingo > Issue Type: Bug >Reporter: Ramya >Priority: Major > > As per the specification > https://www.odata.org/documentation/odata-version-2-0/overview/ Edm Time > should be defined by the lexical representation for dayTimeDuration in > http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration. > Currently if user provides time value like P00DT18H03M08S, we get an error >"Caused by: > org.apache.olingo.odata2.api.ep.EntityProviderException: An exception of type > 'EdmSimpleTypeException' occurred.", >"\t... 107 more", >"Caused by: > org.apache.olingo.odata2.api.edm.EdmSimpleTypeException: The literal > 'P00DT18H03M08S' is not formatted properly.", > "\tat > org.apache.olingo.odata2.core.edm.EdmTime.internalValueOfString(EdmTime.java:71)", -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OLINGO-1367) OData V2: Issue with EdmTime
Ramya created OLINGO-1367: - Summary: OData V2: Issue with EdmTime Key: OLINGO-1367 URL: https://issues.apache.org/jira/browse/OLINGO-1367 Project: Olingo Issue Type: Bug Reporter: Ramya As per the specification https://www.odata.org/documentation/odata-version-2-0/overview/ Edm Time should be defined by the lexical representation for dayTimeDuration in http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration. Currently if user provides time value like P00DT18H03M08S, we get an error "Caused by: org.apache.olingo.odata2.api.ep.EntityProviderException: An exception of type 'EdmSimpleTypeException' occurred.", "\t... 107 more", "Caused by: org.apache.olingo.odata2.api.edm.EdmSimpleTypeException: The literal 'P00DT18H03M08S' is not formatted properly.", "\tat org.apache.olingo.odata2.core.edm.EdmTime.internalValueOfString(EdmTime.java:71)", -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1362) OData V2: Missed http status code 420
[ https://issues.apache.org/jira/browse/OLINGO-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1362. --- Resolution: Fixed > OData V2: Missed http status code 420 > - > > Key: OLINGO-1362 > URL: https://issues.apache.org/jira/browse/OLINGO-1362 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.11 >Reporter: Ramya >Priority: Major > > Http status code 420 is not listed in > org/apache/olingo/odata2/api/commons/HttpStatusCodes.java > 420 http status code is a deprecated response and also it used to be the > return code for Twitter Search and Trends API when the client is being rate > limited. This 420 status code is not added in the olingo HttpStatusCodes and > hence the applications get 500 Internal server error. > (https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1362) OData V2: Missed http status code 420
[ https://issues.apache.org/jira/browse/OLINGO-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855304#comment-16855304 ] Ramya commented on OLINGO-1362: --- This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=8449e389b6166bd9a38473a599d8c7be91c31c20 > OData V2: Missed http status code 420 > - > > Key: OLINGO-1362 > URL: https://issues.apache.org/jira/browse/OLINGO-1362 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.11 >Reporter: Ramya >Priority: Major > > Http status code 420 is not listed in > org/apache/olingo/odata2/api/commons/HttpStatusCodes.java > 420 http status code is a deprecated response and also it used to be the > return code for Twitter Search and Trends API when the client is being rate > limited. This 420 status code is not added in the olingo HttpStatusCodes and > hence the applications get 500 Internal server error. > (https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OLINGO-1362) OData V2: Missed http status code 420
Ramya created OLINGO-1362: - Summary: OData V2: Missed http status code 420 Key: OLINGO-1362 URL: https://issues.apache.org/jira/browse/OLINGO-1362 Project: Olingo Issue Type: Bug Components: odata2-core Affects Versions: V2 2.0.11 Reporter: Ramya Http status code 420 is not listed in org/apache/olingo/odata2/api/commons/HttpStatusCodes.java 420 http status code is a deprecated response and also it used to be the return code for Twitter Search and Trends API when the client is being rate limited. This 420 status code is not added in the olingo HttpStatusCodes and hence the applications get 500 Internal server error. (https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1347) Update V4 documentation on homepage
[
https://issues.apache.org/jira/browse/OLINGO-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramya resolved OLINGO-1347.
---
Resolution: Fixed
> Update V4 documentation on homepage
> ---
>
> Key: OLINGO-1347
> URL: https://issues.apache.org/jira/browse/OLINGO-1347
> Project: Olingo
> Issue Type: Task
>Reporter: mibo
>Priority: Minor
> Fix For: (Java) V4 4.7.0
>
>
> The documentation on the homepage for [OData
> V4|http://olingo.apache.org/doc/odata4/index.html] is still based on version
> {{4.0}}.
> It should be updated to be compliant with the next version {{4.6.0}}.
> Acceptance Criteria:
> - Updated documentation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OLINGO-1347) Update V4 documentation on homepage
[
https://issues.apache.org/jira/browse/OLINGO-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850358#comment-16850358
]
Ramya commented on OLINGO-1347:
---
The documentation on the homepage for OData V4 has been updated to be compliant
with the version 4.6.0.
Kindly reopen the incident if any issues still found.
> Update V4 documentation on homepage
> ---
>
> Key: OLINGO-1347
> URL: https://issues.apache.org/jira/browse/OLINGO-1347
> Project: Olingo
> Issue Type: Task
>Reporter: mibo
>Priority: Minor
> Fix For: (Java) V4 4.7.0
>
>
> The documentation on the homepage for [OData
> V4|http://olingo.apache.org/doc/odata4/index.html] is still based on version
> {{4.0}}.
> It should be updated to be compliant with the next version {{4.6.0}}.
> Acceptance Criteria:
> - Updated documentation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OLINGO-1348) Create V4 client documentation on homepage
[ https://issues.apache.org/jira/browse/OLINGO-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1348. --- Resolution: Fixed > Create V4 client documentation on homepage > -- > > Key: OLINGO-1348 > URL: https://issues.apache.org/jira/browse/OLINGO-1348 > Project: Olingo > Issue Type: Task >Reporter: mibo >Priority: Minor > > The documentation on the homepage for [OData > V4|http://olingo.apache.org/doc/odata4/index.html] is missing a section about > the *Olingo for Client usage* (currently only *Olingo for Server usage* > exists). > It would be nice if this could be added. > Acceptance Criteria: > - New documentation *Olingo for Client usage* on homepage -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1348) Create V4 client documentation on homepage
[ https://issues.apache.org/jira/browse/OLINGO-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849458#comment-16849458 ] Ramya commented on OLINGO-1348: --- Documentation on client usage are added in OData V4 documentation homepage https://olingo.apache.org/doc/odata4/tutorials/od4_basic_client_read.html https://olingo.apache.org/doc/odata4/tutorials/od4_basic_batch_client.html > Create V4 client documentation on homepage > -- > > Key: OLINGO-1348 > URL: https://issues.apache.org/jira/browse/OLINGO-1348 > Project: Olingo > Issue Type: Task >Reporter: mibo >Priority: Minor > > The documentation on the homepage for [OData > V4|http://olingo.apache.org/doc/odata4/index.html] is missing a section about > the *Olingo for Client usage* (currently only *Olingo for Server usage* > exists). > It would be nice if this could be added. > Acceptance Criteria: > - New documentation *Olingo for Client usage* on homepage -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1322) ODATA V2.0: An empty string validation in UriParser
[
https://issues.apache.org/jira/browse/OLINGO-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846539#comment-16846539
]
Ramya commented on OLINGO-1322:
---
As per the specification key can be empty string. Hence reverting the changes
as part of the commit
https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=a941f16db247d3988d6e94f4a9c8775ccb4f0884
> ODATA V2.0: An empty string validation in UriParser
> ---
>
> Key: OLINGO-1322
> URL: https://issues.apache.org/jira/browse/OLINGO-1322
> Project: Olingo
> Issue Type: Improvement
> Components: odata2-core
>Affects Versions: V2 2.0.10
>Reporter: Archana Rai
>Assignee: Archana Rai
>Priority: Minor
> Fix For: V2 2.0.11
>
>
> An empty string does not correspond to any id.
> For e.g. An odata update request on Products, but with a empty string for the
> key-value:
> MERGE Products('')
> This should get validated while uri validation itself rather than getting
> validated in the serializers.
> This will better for performance as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OLINGO-1359) OData V2 Support replace operator in filter
[ https://issues.apache.org/jira/browse/OLINGO-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845619#comment-16845619 ] Ramya commented on OLINGO-1359: --- This is supported as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=5245762de3d300e548c41f1ddb5ff57127075957 > OData V2 Support replace operator in filter > --- > > Key: OLINGO-1359 > URL: https://issues.apache.org/jira/browse/OLINGO-1359 > Project: Olingo > Issue Type: New Feature > Components: odata2-core >Reporter: Ramya >Priority: Major > > According to the specification: > Section 4.5 > https://www.odata.org/documentation/odata-version-2-0/uri-conventions/ > $filter should support replace operator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1359) OData V2 Support replace operator in filter
[ https://issues.apache.org/jira/browse/OLINGO-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1359. --- Resolution: Fixed > OData V2 Support replace operator in filter > --- > > Key: OLINGO-1359 > URL: https://issues.apache.org/jira/browse/OLINGO-1359 > Project: Olingo > Issue Type: New Feature > Components: odata2-core >Reporter: Ramya >Priority: Major > > According to the specification: > Section 4.5 > https://www.odata.org/documentation/odata-version-2-0/uri-conventions/ > $filter should support replace operator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OLINGO-1359) OData V2 Support replace operator in filter
Ramya created OLINGO-1359: - Summary: OData V2 Support replace operator in filter Key: OLINGO-1359 URL: https://issues.apache.org/jira/browse/OLINGO-1359 Project: Olingo Issue Type: New Feature Components: odata2-core Reporter: Ramya According to the specification: Section 4.5 https://www.odata.org/documentation/odata-version-2-0/uri-conventions/ $filter should support replace operator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
