[jira] [Updated] (OLINGO-1406) Release Olingo V4 in version 4.7.0
[ https://issues.apache.org/jira/browse/OLINGO-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1406: - Description: Provide a new Olingo V4 release (version 4.7.0). Recommended steps before: * Check and update (all) dependencies to latest version ** ... Includes: - Release candidate - Voting - Release - Update Distribution - Update Website was: Provide a new Olingo V4 release (version 4.6.0). Recommended steps before: * Update (all) dependencies to latest version ** See e.g. OLINGO-1350 Includes: - Release candidate - Voting - Release - Update Distribution - Update Website > Release Olingo V4 in version 4.7.0 > -- > > Key: OLINGO-1406 > URL: https://issues.apache.org/jira/browse/OLINGO-1406 > Project: Olingo > Issue Type: Task > Components: odata4-client, odata4-commons, odata4-server >Reporter: Michael Bolz >Assignee: mibo >Priority: Major > Fix For: (Java) V4 4.7.0 > > > Provide a new Olingo V4 release (version 4.7.0). > Recommended steps before: > * Check and update (all) dependencies to latest version > ** ... > Includes: > - Release candidate > - Voting > - Release > - Update Distribution > - Update Website -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OLINGO-1406) Release Olingo V4 in version 4.7.0
[ https://issues.apache.org/jira/browse/OLINGO-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1406: - Fix Version/s: (was: (Java) V4 4.6.0) (Java) V4 4.7.0 > Release Olingo V4 in version 4.7.0 > -- > > Key: OLINGO-1406 > URL: https://issues.apache.org/jira/browse/OLINGO-1406 > Project: Olingo > Issue Type: Task > Components: odata4-client, odata4-commons, odata4-server >Reporter: Michael Bolz >Assignee: mibo >Priority: Major > Fix For: (Java) V4 4.7.0 > > > Provide a new Olingo V4 release (version 4.6.0). > Recommended steps before: > * Update (all) dependencies to latest version > ** See e.g. OLINGO-1350 > Includes: > - Release candidate > - Voting > - Release > - Update Distribution > - Update Website -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OLINGO-1406) Release Olingo V4 in version 4.7.0
Michael Bolz created OLINGO-1406: Summary: Release Olingo V4 in version 4.7.0 Key: OLINGO-1406 URL: https://issues.apache.org/jira/browse/OLINGO-1406 Project: Olingo Issue Type: Task Components: odata4-client, odata4-commons, odata4-server Reporter: Michael Bolz Assignee: mibo Fix For: (Java) V4 4.6.0 Provide a new Olingo V4 release (version 4.6.0). Recommended steps before: * Update (all) dependencies to latest version ** See e.g. OLINGO-1350 Includes: - Release candidate - Voting - Release - Update Distribution - Update Website -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OLINGO-1211) netty-all is not a bundle but its dependency adds extra import package to MANIFEST.MF in server-api module
[ https://issues.apache.org/jira/browse/OLINGO-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz resolved OLINGO-1211. -- Resolution: Fixed > netty-all is not a bundle but its dependency adds extra import package to > MANIFEST.MF in server-api module > -- > > Key: OLINGO-1211 > URL: https://issues.apache.org/jira/browse/OLINGO-1211 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.5.0 >Reporter: Dmitri >Assignee: Michael Bolz >Priority: Major > Fix For: (Java) V4 4.6.0 > > > MANIFEST.MF sample: > Import-Package: io.netty.handler.codec.http,... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1211) netty-all is not a bundle but its dependency adds extra import package to MANIFEST.MF in server-api module
[ https://issues.apache.org/jira/browse/OLINGO-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827171#comment-16827171 ] Michael Bolz commented on OLINGO-1211: -- Fixed with [this commit: [\[OLINGO-1211\] Fix imports and bundling|https://gitbox.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=50dec8d5d2b692de9b5dc45243a22dac114c8978]. > netty-all is not a bundle but its dependency adds extra import package to > MANIFEST.MF in server-api module > -- > > Key: OLINGO-1211 > URL: https://issues.apache.org/jira/browse/OLINGO-1211 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.5.0 >Reporter: Dmitri >Assignee: Michael Bolz >Priority: Major > Fix For: (Java) V4 4.6.0 > > > MANIFEST.MF sample: > Import-Package: io.netty.handler.codec.http,... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OLINGO-1343) Deadlocking in PipedInputStream
[ https://issues.apache.org/jira/browse/OLINGO-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz reassigned OLINGO-1343: Assignee: Michael Bolz > Deadlocking in PipedInputStream > --- > > Key: OLINGO-1343 > URL: https://issues.apache.org/jira/browse/OLINGO-1343 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.5.0, (Java) V4 4.6.0 >Reporter: Aleksandr Zaigraev >Assignee: Michael Bolz >Priority: Blocker > Labels: patch > Fix For: (Java) V4 4.6.0 > > Attachments: OLINGO-1343.patch, deadlock_1.txt > > > Deadlocking in PipedInputStream often happens on communication errors (e.g. > proxy timeouts) when using Olingo with Spring Batch: > "spring_batch13" #46 prio=5 os_prio=0 tid=0x250e0800 nid=0xf50 in > Object.wait() [0x2d42e000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.io.PipedInputStream.awaitSpace(PipedInputStream.java:273) > at java.io.PipedInputStream.receive(PipedInputStream.java:231) > - locked <0x00075f4ccfd8> (a java.io.PipedInputStream) > at java.io.PipedOutputStream.write(PipedOutputStream.java:149) > at java.io.OutputStream.write(OutputStream.java:75) > at > org.apache.olingo.client.core.communication.request.batch.ODataBatchRequestImpl.rawAppend(ODataBatchRequestImpl.java:57) > at > org.apache.olingo.client.core.communication.request.AbstractODataBasicRequest.batch(AbstractODataBasicRequest.java:107) > at > org.apache.olingo.client.core.communication.request.batch.ODataChangesetImpl.addRequest(ODataChangesetImpl.java:125) > > Full thread dump in attached file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1349) EdmTime use synchronized TimeZone.getTimeZone("GMT")
[
https://issues.apache.org/jira/browse/OLINGO-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz resolved OLINGO-1349.
--
Resolution: Fixed
Hi [~psteuer],
the update is pushed to master and will be available with next release.
If the solution works for you please close this issue otherwise re-open and
comment.
Regards, Michael
> EdmTime use synchronized TimeZone.getTimeZone("GMT")
>
>
> Key: OLINGO-1349
> URL: https://issues.apache.org/jira/browse/OLINGO-1349
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.11
>Reporter: Patrik Steuer
>Assignee: Michael Bolz
>Priority: Major
> Fix For: V2 2.0.12
>
>
> *Problem:*
> [EdmTime.class:internalValueToString|https://github.com/apache/olingo-odata2/blob/master/odata2-lib/odata-core/src/main/java/org/apache/olingo/odata2/core/edm/EdmTime.java#L132]
> calls TimeZone.getTimeZone("GMT") which is synchronized. This adds overhead
> to apps using this function.
> *Possible Solution:*
> Either use a more modern class like ZoneId.of() or use a static variable to
> reuse the timezone.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OLINGO-1349) EdmTime use synchronized TimeZone.getTimeZone("GMT")
[
https://issues.apache.org/jira/browse/OLINGO-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-1349:
-
Fix Version/s: V2 2.0.12
> EdmTime use synchronized TimeZone.getTimeZone("GMT")
>
>
> Key: OLINGO-1349
> URL: https://issues.apache.org/jira/browse/OLINGO-1349
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.11
>Reporter: Patrik Steuer
>Assignee: Michael Bolz
>Priority: Major
> Fix For: V2 2.0.12
>
>
> *Problem:*
> [EdmTime.class:internalValueToString|https://github.com/apache/olingo-odata2/blob/master/odata2-lib/odata-core/src/main/java/org/apache/olingo/odata2/core/edm/EdmTime.java#L132]
> calls TimeZone.getTimeZone("GMT") which is synchronized. This adds overhead
> to apps using this function.
> *Possible Solution:*
> Either use a more modern class like ZoneId.of() or use a static variable to
> reuse the timezone.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OLINGO-1349) EdmTime use synchronized TimeZone.getTimeZone("GMT")
[
https://issues.apache.org/jira/browse/OLINGO-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16824859#comment-16824859
]
Michael Bolz commented on OLINGO-1349:
--
Hi [~psteuer],
For Olingo 2.x we still stick to Java 1.6 compatibility. Hence use of
{{ZoneId}} is not possible.
However store the TimeZone to a static field should solve the
synchronized/performance issue.
I created a [branch with a possible
solution|https://gitbox.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=cd2db731c9df27a45ae97346ccc5fc5665e83473].
Please let me know if you think this solve your issue (or ideally test it and
let us know your result).
Kind Regards, Michael
> EdmTime use synchronized TimeZone.getTimeZone("GMT")
>
>
> Key: OLINGO-1349
> URL: https://issues.apache.org/jira/browse/OLINGO-1349
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.11
>Reporter: Patrik Steuer
>Assignee: Michael Bolz
>Priority: Major
>
> *Problem:*
> [EdmTime.class:internalValueToString|https://github.com/apache/olingo-odata2/blob/master/odata2-lib/odata-core/src/main/java/org/apache/olingo/odata2/core/edm/EdmTime.java#L132]
> calls TimeZone.getTimeZone("GMT") which is synchronized. This adds overhead
> to apps using this function.
> *Possible Solution:*
> Either use a more modern class like ZoneId.of() or use a static variable to
> reuse the timezone.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OLINGO-1349) EdmTime use synchronized TimeZone.getTimeZone("GMT")
[
https://issues.apache.org/jira/browse/OLINGO-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz reassigned OLINGO-1349:
Assignee: Michael Bolz
> EdmTime use synchronized TimeZone.getTimeZone("GMT")
>
>
> Key: OLINGO-1349
> URL: https://issues.apache.org/jira/browse/OLINGO-1349
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.11
>Reporter: Patrik Steuer
>Assignee: Michael Bolz
>Priority: Major
>
> *Problem:*
> [EdmTime.class:internalValueToString|https://github.com/apache/olingo-odata2/blob/master/odata2-lib/odata-core/src/main/java/org/apache/olingo/odata2/core/edm/EdmTime.java#L132]
> calls TimeZone.getTimeZone("GMT") which is synchronized. This adds overhead
> to apps using this function.
> *Possible Solution:*
> Either use a more modern class like ZoneId.of() or use a static variable to
> reuse the timezone.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OLINGO-1344) Deadlocking in internal ThreadPool
[ https://issues.apache.org/jira/browse/OLINGO-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz reassigned OLINGO-1344: Assignee: Michael Bolz > Deadlocking in internal ThreadPool > -- > > Key: OLINGO-1344 > URL: https://issues.apache.org/jira/browse/OLINGO-1344 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.5.0, (Java) V4 4.6.0 >Reporter: Aleksandr Zaigraev >Assignee: Michael Bolz >Priority: Blocker > Labels: patch > Fix For: (Java) V4 4.6.0 > > Attachments: OLINGO-1344.patch, deadlock_2.txt > > > Deadlocking in internal ThreadPool often happens in case of connection errors > (e.g. proxy timeouts): > "spring_batch56" #86 prio=5 os_prio=0 tid=0x21577800 nid=0x8388 > waiting on condition [0x2cefe000] > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x0007608ec330> (a > java.util.concurrent.FutureTask) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:426) > at java.util.concurrent.FutureTask.get(FutureTask.java:204) > at > org.apache.olingo.client.core.communication.request.AbstractODataStreamManager.getHttpResponse(AbstractODataStreamManager.java:125) > at > org.apache.olingo.client.core.communication.request.batch.ODataBatchRequestImpl$BatchManagerImpl.getResponseInstance(ODataBatchRequestImpl.java:88) > at > org.apache.olingo.client.core.communication.request.batch.AbstractBatchManager.getResponse(AbstractBatchManager.java:115) > at > org.apache.olingo.client.core.communication.request.batch.AbstractBatchManager.getResponse(AbstractBatchManager.java:38) > at > org.apache.olingo.client.core.communication.request.AbstractODataStreamManager$1.get(AbstractODataStreamManager.java:179) > at > org.apache.olingo.client.core.communication.request.AbstractODataStreamManager$1.get(AbstractODataStreamManager.java:154) > Full thread dump attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OLINGO-1211) netty-all is not a bundle but its dependency adds extra import package to MANIFEST.MF in server-api module
[ https://issues.apache.org/jira/browse/OLINGO-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz reassigned OLINGO-1211: Assignee: Michael Bolz > netty-all is not a bundle but its dependency adds extra import package to > MANIFEST.MF in server-api module > -- > > Key: OLINGO-1211 > URL: https://issues.apache.org/jira/browse/OLINGO-1211 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.5.0 >Reporter: Dmitri >Assignee: Michael Bolz >Priority: Major > Fix For: (Java) V4 4.6.0 > > > MANIFEST.MF sample: > Import-Package: io.netty.handler.codec.http,... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1332) Header Perfer: "return=minimal" or "return=representation" return Error "Prefer Header not supported"
[
https://issues.apache.org/jira/browse/OLINGO-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz resolved OLINGO-1332.
--
Resolution: Not A Problem
> Header Perfer: "return=minimal" or "return=representation" return Error
> "Prefer Header not supported"
> -
>
> Key: OLINGO-1332
> URL: https://issues.apache.org/jira/browse/OLINGO-1332
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
>Affects Versions: (Java) V4 4.5.0
>Reporter: Jerome BAROTIN
>Assignee: Michael Bolz
>Priority: Major
> Attachments: OLINGO-1332.patch
>
>
>
> Hi,
> {color:#33}Considering the following python script :{color}
> {code:java}
> # -*- encoding: utf-8 -*-
> import requests
> headers = {
> 'Content-Type': 'application/json',
> 'Prefer': 'return=minimal'
> }
> url = "http://localhost:8080/Customers(2)"
> r = requests.get(url, headers=headers))
> print(r.content){code}
> If I run it on my olingo implementation, I've got the following content :
> {noformat}
> b'{"error":{"code":null,"message":"The Prefer header \'return=minimal\' is
> not supported for this HTTP Method."}}'{noformat}
>
>
>
>
> {color:#808080} {color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OLINGO-1332) Header Perfer: "return=minimal" or "return=representation" return Error "Prefer Header not supported"
[
https://issues.apache.org/jira/browse/OLINGO-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821792#comment-16821792
]
Michael Bolz commented on OLINGO-1332:
--
Yes, it looks like that the bug is in the .net "Simple.OData.Client" library.
I will close this issue for now.
But feel free to comment or reopen it if necessary.
> Header Perfer: "return=minimal" or "return=representation" return Error
> "Prefer Header not supported"
> -
>
> Key: OLINGO-1332
> URL: https://issues.apache.org/jira/browse/OLINGO-1332
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
>Affects Versions: (Java) V4 4.5.0
>Reporter: Jerome BAROTIN
>Assignee: Michael Bolz
>Priority: Major
> Attachments: OLINGO-1332.patch
>
>
>
> Hi,
> {color:#33}Considering the following python script :{color}
> {code:java}
> # -*- encoding: utf-8 -*-
> import requests
> headers = {
> 'Content-Type': 'application/json',
> 'Prefer': 'return=minimal'
> }
> url = "http://localhost:8080/Customers(2)"
> r = requests.get(url, headers=headers))
> print(r.content){code}
> If I run it on my olingo implementation, I've got the following content :
> {noformat}
> b'{"error":{"code":null,"message":"The Prefer header \'return=minimal\' is
> not supported for this HTTP Method."}}'{noformat}
>
>
>
>
> {color:#808080} {color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OLINGO-1332) Header Perfer: "return=minimal" or "return=representation" return Error "Prefer Header not supported"
[
https://issues.apache.org/jira/browse/OLINGO-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-1332:
-
Fix Version/s: (was: (Java) V4 4.6.0)
> Header Perfer: "return=minimal" or "return=representation" return Error
> "Prefer Header not supported"
> -
>
> Key: OLINGO-1332
> URL: https://issues.apache.org/jira/browse/OLINGO-1332
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
>Affects Versions: (Java) V4 4.5.0
>Reporter: Jerome BAROTIN
>Assignee: Michael Bolz
>Priority: Major
> Attachments: OLINGO-1332.patch
>
>
>
> Hi,
> {color:#33}Considering the following python script :{color}
> {code:java}
> # -*- encoding: utf-8 -*-
> import requests
> headers = {
> 'Content-Type': 'application/json',
> 'Prefer': 'return=minimal'
> }
> url = "http://localhost:8080/Customers(2)"
> r = requests.get(url, headers=headers))
> print(r.content){code}
> If I run it on my olingo implementation, I've got the following content :
> {noformat}
> b'{"error":{"code":null,"message":"The Prefer header \'return=minimal\' is
> not supported for this HTTP Method."}}'{noformat}
>
>
>
>
> {color:#808080} {color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OLINGO-1332) Header Perfer: "return=minimal" or "return=representation" return Error "Prefer Header not supported"
[
https://issues.apache.org/jira/browse/OLINGO-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821398#comment-16821398
]
Michael Bolz commented on OLINGO-1332:
--
Hello [~jbarotin],
Sorry for the delay.
However regarding your fix in OData V4 [8.2.8.7 Preference
return=representation and
return=minimal|http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752234]
it is defined that:
{quote}
In OData, return=representation or return=minimal is defined for use with a
POST, PUT, or PATCH Data Modification Request other than to a stream property,
or to an Action Request. Specifying a preference of return=representation or
return=minimal in a GET or DELETE request, or any request to a stream property,
SHOULD return a 4xx Client Error.
{quote}
So as I understand your case you receive an error if you add {{Prefer':
'return=minimal'}} in a {{GET}} HTTP request.
If yes then this is the behaviour as defined in OData V4.
If not please help me in explain your issue in more detail.
Kind Regards, Michael
> Header Perfer: "return=minimal" or "return=representation" return Error
> "Prefer Header not supported"
> -
>
> Key: OLINGO-1332
> URL: https://issues.apache.org/jira/browse/OLINGO-1332
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
>Affects Versions: (Java) V4 4.5.0
>Reporter: Jerome BAROTIN
>Assignee: Michael Bolz
>Priority: Major
> Fix For: (Java) V4 4.6.0
>
> Attachments: OLINGO-1332.patch
>
>
>
> Hi,
> {color:#33}Considering the following python script :{color}
> {code:java}
> # -*- encoding: utf-8 -*-
> import requests
> headers = {
> 'Content-Type': 'application/json',
> 'Prefer': 'return=minimal'
> }
> url = "http://localhost:8080/Customers(2)"
> r = requests.get(url, headers=headers))
> print(r.content){code}
> If I run it on my olingo implementation, I've got the following content :
> {noformat}
> b'{"error":{"code":null,"message":"The Prefer header \'return=minimal\' is
> not supported for this HTTP Method."}}'{noformat}
>
>
>
>
> {color:#808080} {color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OLINGO-1332) Header Perfer: "return=minimal" or "return=representation" return Error "Prefer Header not supported"
[
https://issues.apache.org/jira/browse/OLINGO-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-1332:
-
Fix Version/s: (Java) V4 4.6.0
> Header Perfer: "return=minimal" or "return=representation" return Error
> "Prefer Header not supported"
> -
>
> Key: OLINGO-1332
> URL: https://issues.apache.org/jira/browse/OLINGO-1332
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
>Affects Versions: (Java) V4 4.5.0
>Reporter: Jerome BAROTIN
>Assignee: Michael Bolz
>Priority: Major
> Fix For: (Java) V4 4.6.0
>
> Attachments: OLINGO-1332.patch
>
>
>
> Hi,
> {color:#33}Considering the following python script :{color}
> {code:java}
> # -*- encoding: utf-8 -*-
> import requests
> headers = {
> 'Content-Type': 'application/json',
> 'Prefer': 'return=minimal'
> }
> url = "http://localhost:8080/Customers(2)"
> r = requests.get(url, headers=headers))
> print(r.content){code}
> If I run it on my olingo implementation, I've got the following content :
> {noformat}
> b'{"error":{"code":null,"message":"The Prefer header \'return=minimal\' is
> not supported for this HTTP Method."}}'{noformat}
>
>
>
>
> {color:#808080} {color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OLINGO-1347) Update documentation on homepage
Michael Bolz created OLINGO-1347:
Summary: Update documentation on homepage
Key: OLINGO-1347
URL: https://issues.apache.org/jira/browse/OLINGO-1347
Project: Olingo
Issue Type: Task
Reporter: Michael Bolz
Fix For: (Java) V4 4.6.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] [Updated] (OLINGO-1343) Deadlocking in PipedInputStream
[ https://issues.apache.org/jira/browse/OLINGO-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1343: - Fix Version/s: (was: (Java) V4 4.5.0) > Deadlocking in PipedInputStream > --- > > Key: OLINGO-1343 > URL: https://issues.apache.org/jira/browse/OLINGO-1343 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.5.0, (Java) V4 4.6.0 >Reporter: Aleksandr Zaigraev >Priority: Blocker > Labels: patch > Fix For: (Java) V4 4.6.0 > > Attachments: OLINGO-1343.patch, deadlock_1.txt > > > Deadlocking in PipedInputStream often happens on communication errors (e.g. > proxy timeouts) when using Olingo with Spring Batch: > "spring_batch13" #46 prio=5 os_prio=0 tid=0x250e0800 nid=0xf50 in > Object.wait() [0x2d42e000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.io.PipedInputStream.awaitSpace(PipedInputStream.java:273) > at java.io.PipedInputStream.receive(PipedInputStream.java:231) > - locked <0x00075f4ccfd8> (a java.io.PipedInputStream) > at java.io.PipedOutputStream.write(PipedOutputStream.java:149) > at java.io.OutputStream.write(OutputStream.java:75) > at > org.apache.olingo.client.core.communication.request.batch.ODataBatchRequestImpl.rawAppend(ODataBatchRequestImpl.java:57) > at > org.apache.olingo.client.core.communication.request.AbstractODataBasicRequest.batch(AbstractODataBasicRequest.java:107) > at > org.apache.olingo.client.core.communication.request.batch.ODataChangesetImpl.addRequest(ODataChangesetImpl.java:125) > > Full thread dump in attached file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1344) Deadlocking in internal ThreadPool
[ https://issues.apache.org/jira/browse/OLINGO-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1344: - Fix Version/s: (was: (Java) V4 4.5.0) > Deadlocking in internal ThreadPool > -- > > Key: OLINGO-1344 > URL: https://issues.apache.org/jira/browse/OLINGO-1344 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.5.0, (Java) V4 4.6.0 >Reporter: Aleksandr Zaigraev >Priority: Blocker > Labels: patch > Fix For: (Java) V4 4.6.0 > > Attachments: OLINGO-1344.patch, deadlock_2.txt > > > Deadlocking in internal ThreadPool often happens in case of connection errors > (e.g. proxy timeouts): > "spring_batch56" #86 prio=5 os_prio=0 tid=0x21577800 nid=0x8388 > waiting on condition [0x2cefe000] > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x0007608ec330> (a > java.util.concurrent.FutureTask) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:426) > at java.util.concurrent.FutureTask.get(FutureTask.java:204) > at > org.apache.olingo.client.core.communication.request.AbstractODataStreamManager.getHttpResponse(AbstractODataStreamManager.java:125) > at > org.apache.olingo.client.core.communication.request.batch.ODataBatchRequestImpl$BatchManagerImpl.getResponseInstance(ODataBatchRequestImpl.java:88) > at > org.apache.olingo.client.core.communication.request.batch.AbstractBatchManager.getResponse(AbstractBatchManager.java:115) > at > org.apache.olingo.client.core.communication.request.batch.AbstractBatchManager.getResponse(AbstractBatchManager.java:38) > at > org.apache.olingo.client.core.communication.request.AbstractODataStreamManager$1.get(AbstractODataStreamManager.java:179) > at > org.apache.olingo.client.core.communication.request.AbstractODataStreamManager$1.get(AbstractODataStreamManager.java:154) > Full thread dump attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1342) Non-json errors not displayed properly in logs
[
https://issues.apache.org/jira/browse/OLINGO-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-1342:
-
Fix Version/s: (was: (Java) V4 4.5.0)
> Non-json errors not displayed properly in logs
> --
>
> Key: OLINGO-1342
> URL: https://issues.apache.org/jira/browse/OLINGO-1342
> Project: Olingo
> Issue Type: Bug
> Components: odata4-client
>Affects Versions: (Java) V4 4.5.0, (Java) V4 4.6.0
>Reporter: Aleksandr Zaigraev
>Priority: Major
> Labels: patch
> Fix For: (Java) V4 4.6.0
>
> Attachments: OLINGO-1342.patch
>
>
> When http client receives non-json encoded error message, for example when
> receiving this error message:
> Tunnel Connection Failed...
> In Spring logs following will be displayed:
> org.apache.olingo.client.api.serialization.ODataDeserializerException:
> com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<'
> (code 60)): expected a valid value (number, String, array, object, 'true',
> 'false' or 'null')
> at [Source: (ByteArrayInputStream); line: 1, column: 2]
> at
> org.apache.olingo.client.core.serialization.JsonDeserializer.toError(JsonDeserializer.java:444)
> ~[odata-client-core-4.5.0.jar:na]
> at
> org.apache.olingo.client.core.serialization.ClientODataDeserializerImpl.toError(ClientODataDeserializerImpl.java:105)
> ~[odata-client-core-4.5.0.jar:na]
> ...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (OLINGO-619) POC: Module odata-jpa-api
[ https://issues.apache.org/jira/browse/OLINGO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz closed OLINGO-619. --- Resolution: Later Set this to *LATER* because it is affects very old beta and there was no action in the last three years. > POC: Module odata-jpa-api > - > > Key: OLINGO-619 > URL: https://issues.apache.org/jira/browse/OLINGO-619 > Project: Olingo > Issue Type: Sub-task > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A >Priority: Major > Fix For: (JPA) V4 4.0.0-beta-01 > > > Proposal - > The module odata-jpa-api shall contain > 1) ODataJPAServlet for handling OData request and response in the context of > JPA processor > 2) ODataJPAEdmProvider for producing OData V4 complaint metadata from JPA > Entity Model > 3) ODataJPAProcessor a root processor for handing OData V4 complaint requests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1339) Typo on download page(s)
[ https://issues.apache.org/jira/browse/OLINGO-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770799#comment-16770799 ] Michael Bolz commented on OLINGO-1339: -- Hi [~s...@apache.org], Thanks for the hint and improvement proposal. I checked the whole homepage and changed further parts. Kind Regards, Michael > Typo on download page(s) > > > Key: OLINGO-1339 > URL: https://issues.apache.org/jira/browse/OLINGO-1339 > Project: Olingo > Issue Type: Bug >Reporter: Sebb >Assignee: Michael Bolz >Priority: Major > > The download page [1] twice refers to a 'productive environment'. > I think that should be 'production environment'. > Productive means "*having > [positive|https://dictionary.cambridge.org/dictionary/english/positive] > [results|https://dictionary.cambridge.org/dictionary/english/result]*; or > "*[providing|https://dictionary.cambridge.org/dictionary/english/provide] a > [large|https://dictionary.cambridge.org/dictionary/english/large] > [amount|https://dictionary.cambridge.org/dictionary/english/amount] or > [supply|https://dictionary.cambridge.org/dictionary/english/supply] of > something*". > There may be other instances of the phrase on other pages. > [1] http://olingo.apache.org/doc/odata2/download.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1339) Typo on download page(s)
[ https://issues.apache.org/jira/browse/OLINGO-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz resolved OLINGO-1339. -- Resolution: Fixed > Typo on download page(s) > > > Key: OLINGO-1339 > URL: https://issues.apache.org/jira/browse/OLINGO-1339 > Project: Olingo > Issue Type: Bug >Reporter: Sebb >Assignee: Michael Bolz >Priority: Major > > The download page [1] twice refers to a 'productive environment'. > I think that should be 'production environment'. > Productive means "*having > [positive|https://dictionary.cambridge.org/dictionary/english/positive] > [results|https://dictionary.cambridge.org/dictionary/english/result]*; or > "*[providing|https://dictionary.cambridge.org/dictionary/english/provide] a > [large|https://dictionary.cambridge.org/dictionary/english/large] > [amount|https://dictionary.cambridge.org/dictionary/english/amount] or > [supply|https://dictionary.cambridge.org/dictionary/english/supply] of > something*". > There may be other instances of the phrase on other pages. > [1] http://olingo.apache.org/doc/odata2/download.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OLINGO-1339) Typo on download page(s)
[ https://issues.apache.org/jira/browse/OLINGO-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz reassigned OLINGO-1339: Assignee: Michael Bolz > Typo on download page(s) > > > Key: OLINGO-1339 > URL: https://issues.apache.org/jira/browse/OLINGO-1339 > Project: Olingo > Issue Type: Bug >Reporter: Sebb >Assignee: Michael Bolz >Priority: Major > > The download page [1] twice refers to a 'productive environment'. > I think that should be 'production environment'. > Productive means "*having > [positive|https://dictionary.cambridge.org/dictionary/english/positive] > [results|https://dictionary.cambridge.org/dictionary/english/result]*; or > "*[providing|https://dictionary.cambridge.org/dictionary/english/provide] a > [large|https://dictionary.cambridge.org/dictionary/english/large] > [amount|https://dictionary.cambridge.org/dictionary/english/amount] or > [supply|https://dictionary.cambridge.org/dictionary/english/supply] of > something*". > There may be other instances of the phrase on other pages. > [1] http://olingo.apache.org/doc/odata2/download.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1335) Release Olingo V2 in version 2.0.11
[ https://issues.apache.org/jira/browse/OLINGO-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz resolved OLINGO-1335. -- Resolution: Fixed Fix Version/s: (was: V2 2.0.12) V2 2.0.11 All done > Release Olingo V2 in version 2.0.11 > --- > > Key: OLINGO-1335 > URL: https://issues.apache.org/jira/browse/OLINGO-1335 > Project: Olingo > Issue Type: Task > Components: odata2-annotation, odata2-core, odata2-documentation, > odata2-jpa >Affects Versions: V2 2.0.11 >Reporter: Michael Bolz >Assignee: Michael Bolz >Priority: Major > Fix For: V2 2.0.11 > > > Provide a new Olingo V2 release (version 2.0.11). > Includes: > - Release candidate > - Voting > - Release > - Update Distribution > - Update Website -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OLINGO-1335) Release Olingo V2 in version 2.0.11
[ https://issues.apache.org/jira/browse/OLINGO-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz closed OLINGO-1335. > Release Olingo V2 in version 2.0.11 > --- > > Key: OLINGO-1335 > URL: https://issues.apache.org/jira/browse/OLINGO-1335 > Project: Olingo > Issue Type: Task > Components: odata2-annotation, odata2-core, odata2-documentation, > odata2-jpa >Affects Versions: V2 2.0.11 >Reporter: Michael Bolz >Assignee: Michael Bolz >Priority: Major > Fix For: V2 2.0.11 > > > Provide a new Olingo V2 release (version 2.0.11). > Includes: > - Release candidate > - Voting > - Release > - Update Distribution > - Update Website -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1219) When nullable key is defined Encoder would throw NPE
[
https://issues.apache.org/jira/browse/OLINGO-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-1219:
-
Fix Version/s: (was: V2 2.0.10)
> When nullable key is defined Encoder would throw NPE
>
>
> Key: OLINGO-1219
> URL: https://issues.apache.org/jira/browse/OLINGO-1219
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.9
>Reporter: Song Yihan
>Priority: Major
>
> in current Encoder implementation, if given input is null, an NPE would be
> thrown
> The scenario would be, consider an Entity which key is allowed to be null in
> Edmx, thus, the data retrieved in data source would be a HashMap only with
> non-null value, when createEntryKey<-createSelfLink, we generate the key
> representation from the given data, some of the key would be null and passed
> to Encoder, which would throw NullPointerException and skip the check of its
> corresponding facets
> if (value == null) {
> if (facets == null || facets.isNullable() == null ||
> facets.isNullable()) {
> return null;
> } else {
> throw new
> EdmSimpleTypeException(EdmSimpleTypeException.VALUE_NULL_NOT_ALLOWED);
> }
> }
> A pull request has been created aim to fix it at
> https://github.com/apache/olingo-odata2/pull/14
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OLINGO-1335) Release Olingo V2 in version 2.0.11
[ https://issues.apache.org/jira/browse/OLINGO-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1335: - Fix Version/s: (was: V2 2.0.11) V2 2.0.12 > Release Olingo V2 in version 2.0.11 > --- > > Key: OLINGO-1335 > URL: https://issues.apache.org/jira/browse/OLINGO-1335 > Project: Olingo > Issue Type: Task > Components: odata2-annotation, odata2-core, odata2-documentation, > odata2-jpa >Affects Versions: V2 2.0.11 >Reporter: Michael Bolz >Assignee: Michael Bolz >Priority: Major > Fix For: V2 2.0.12 > > > Provide a new Olingo V2 release (version 2.0.11). > Includes: > - Release candidate > - Voting > - Release > - Update Distribution > - Update Website -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OLINGO-1332) Header Perfer: "return=minimal" or "return=representation" return Error "Prefer Header not supported"
[
https://issues.apache.org/jira/browse/OLINGO-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz reassigned OLINGO-1332:
Assignee: Michael Bolz
> Header Perfer: "return=minimal" or "return=representation" return Error
> "Prefer Header not supported"
> -
>
> Key: OLINGO-1332
> URL: https://issues.apache.org/jira/browse/OLINGO-1332
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
>Affects Versions: (Java) V4 4.5.0
>Reporter: Jerome BAROTIN
>Assignee: Michael Bolz
>Priority: Major
> Attachments: OLINGO-1332.patch
>
>
>
> Hi,
> {color:#33}Considering the following python script :{color}
> {code:java}
> # -*- encoding: utf-8 -*-
> import requests
> headers = {
> 'Content-Type': 'application/json',
> 'Prefer': 'return=minimal'
> }
> url = "http://localhost:8080/Customers(2)"
> r = requests.get(url, headers=headers))
> print(r.content){code}
> If I run it on my olingo implementation, I've got the following content :
> {noformat}
> b'{"error":{"code":null,"message":"The Prefer header \'return=minimal\' is
> not supported for this HTTP Method."}}'{noformat}
>
>
>
>
> {color:#808080} {color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OLINGO-1335) Release Olingo V2 in version 2.0.11
Michael Bolz created OLINGO-1335: Summary: Release Olingo V2 in version 2.0.11 Key: OLINGO-1335 URL: https://issues.apache.org/jira/browse/OLINGO-1335 Project: Olingo Issue Type: Task Components: odata2-annotation, odata2-core, odata2-documentation, odata2-jpa Affects Versions: V2 2.0.11 Reporter: Michael Bolz Fix For: V2 2.0.11 Provide a new Olingo V2 release (version 2.0.11). Includes: - Release candidate - Voting - Release - Update Distribution - Update Website -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OLINGO-1335) Release Olingo V2 in version 2.0.11
[ https://issues.apache.org/jira/browse/OLINGO-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz reassigned OLINGO-1335: Assignee: Michael Bolz > Release Olingo V2 in version 2.0.11 > --- > > Key: OLINGO-1335 > URL: https://issues.apache.org/jira/browse/OLINGO-1335 > Project: Olingo > Issue Type: Task > Components: odata2-annotation, odata2-core, odata2-documentation, > odata2-jpa >Affects Versions: V2 2.0.11 >Reporter: Michael Bolz >Assignee: Michael Bolz >Priority: Major > Fix For: V2 2.0.11 > > > Provide a new Olingo V2 release (version 2.0.11). > Includes: > - Release candidate > - Voting > - Release > - Update Distribution > - Update Website -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1286) Builds failing for version 2.0.11-snapshots
[ https://issues.apache.org/jira/browse/OLINGO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754134#comment-16754134 ] Michael Bolz commented on OLINGO-1286: -- Hi [~shivasaxena], Can you please post some information about your build environment. Especially used Java version and JVM vendor. Kind Regards, Michael > Builds failing for version 2.0.11-snapshots > --- > > Key: OLINGO-1286 > URL: https://issues.apache.org/jira/browse/OLINGO-1286 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.11 >Reporter: Shiva Saxena >Assignee: Michael Bolz >Priority: Major > > Olingo 2.0.11-Snapshot builds are failing for component > olingo-odata2-jpa-processor-core > > Actual error message > Tests in error: > > buildQueryGetEntitySetTestWithNoNormalizationWithSubstringof(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithSubstringof(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithStartsWith(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNoNormalizationWithStartsWith(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithEndsWith(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNoNormalizationWithEndsWith(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithSubstring(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNoNormalizationWithSubstring(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithtoLower(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNoNormalizationWithtoLower(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithSubstringof1(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryValueNormalizeTest(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryNormalizeTest(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > Please fix the builds as I was trying to commit some fixes to other issues, > and its had to develop if the project is not in consistent state -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OLINGO-1286) Builds failing for version 2.0.11-snapshots
[ https://issues.apache.org/jira/browse/OLINGO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz reassigned OLINGO-1286: Assignee: Michael Bolz > Builds failing for version 2.0.11-snapshots > --- > > Key: OLINGO-1286 > URL: https://issues.apache.org/jira/browse/OLINGO-1286 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.11 >Reporter: Shiva Saxena >Assignee: Michael Bolz >Priority: Major > > Olingo 2.0.11-Snapshot builds are failing for component > olingo-odata2-jpa-processor-core > > Actual error message > Tests in error: > > buildQueryGetEntitySetTestWithNoNormalizationWithSubstringof(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithSubstringof(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithStartsWith(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNoNormalizationWithStartsWith(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithEndsWith(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNoNormalizationWithEndsWith(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithSubstring(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNoNormalizationWithSubstring(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithtoLower(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNoNormalizationWithtoLower(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryGetEntitySetTestWithNormalizationWithSubstringof1(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryValueNormalizeTest(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > buildQueryNormalizeTest(org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilderTest): > Unresolved compilation problem: (..) > > Please fix the builds as I was trying to commit some fixes to other issues, > and its had to develop if the project is not in consistent state -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-883) Datetime literal is case sensitive
[
https://issues.apache.org/jira/browse/OLINGO-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-883:
Fix Version/s: (was: V2 2.0.7)
> Datetime literal is case sensitive
> --
>
> Key: OLINGO-883
> URL: https://issues.apache.org/jira/browse/OLINGO-883
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.5
>Reporter: Dirk Mahler
>Assignee: Christian Amend
>Priority: Major
>
> We're using Spotfire's ODATA connector to retrieve data. For datetime columns
> the following filter is generated:
> {code}
> MyTimeStamp ge DateTime'2016-01-01T00:00:00'
> {code}
> Olingo fails parsing the filter because it expects "DateTime" to be in
> lower-case, i.e. "datetime"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OLINGO-1050) Supporting function import in annotation based with odatasingle processor
[ https://issues.apache.org/jira/browse/OLINGO-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1050: - Fix Version/s: (was: V2 2.0.7) > Supporting function import in annotation based with odatasingle processor > - > > Key: OLINGO-1050 > URL: https://issues.apache.org/jira/browse/OLINGO-1050 > Project: Olingo > Issue Type: Improvement > Components: odata2-annotation >Affects Versions: V2 2.0.7 > Environment: function import in annotation based with odatasingle > processor >Reporter: sonali jha >Priority: Major > Labels: patch > Original Estimate: 168h > Remaining Estimate: 168h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1205) Edm.GeographyCollection and Edm.GeometryCollection type is not working for MultiLineString and MultiPolygon type
[ https://issues.apache.org/jira/browse/OLINGO-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1205: - Fix Version/s: (was: (Java) V4 4.4.0) > Edm.GeographyCollection and Edm.GeometryCollection type is not working for > MultiLineString and MultiPolygon type > - > > Key: OLINGO-1205 > URL: https://issues.apache.org/jira/browse/OLINGO-1205 > Project: Olingo > Issue Type: Bug > Components: odata4-commons >Affects Versions: (Java) V4 4.4.0 >Reporter: Dattatray >Priority: Major > > I have given following string representation for Edm.GeographyCollection > and Edm.GeometryCollection > 1]Edm.GeographyCollection => > geography'SRID=0;Collection(MultiLineString((142.1 64.1,3.14 2.78),(142.1 > 64.7,3.14 2.78)))' > 2]Edm.GeographyCollection =>geography'SRID=0;Collection(MultiPolygon(((1 1,1 > 1),(1 1,2 2,3 3,1 1)),((1 1,1 1),(1 1,2 2,3 3,1 1' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1284) V4: Build 4.5.0 release
[ https://issues.apache.org/jira/browse/OLINGO-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716541#comment-16716541 ] Michael Bolz commented on OLINGO-1284: -- Add the related tag [4.5.0|https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=7290f7ea4dc6e4096ec85c47f6012dcc24458e5c]. [~davidmoten2]: Sorry for the delay. Regards, Michael > V4: Build 4.5.0 release > --- > > Key: OLINGO-1284 > URL: https://issues.apache.org/jira/browse/OLINGO-1284 > Project: Olingo > Issue Type: Task > Components: odata4-client, odata4-commons, odata4-ext, odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Christian Amend >Assignee: Christian Amend >Priority: Major > Fix For: (Java) V4 4.5.0 > > > Build the 4.5.0 release > Tasks: > Release Candidate > Upload to storage > Start Voting > Upload to Maven Central > Upload to release store > Update JavaDoc > Send Release Mail to announce mailing list -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OLINGO-1284) V4: Build 4.5.0 release
[ https://issues.apache.org/jira/browse/OLINGO-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz closed OLINGO-1284. > V4: Build 4.5.0 release > --- > > Key: OLINGO-1284 > URL: https://issues.apache.org/jira/browse/OLINGO-1284 > Project: Olingo > Issue Type: Task > Components: odata4-client, odata4-commons, odata4-ext, odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Christian Amend >Assignee: Christian Amend >Priority: Major > Fix For: (Java) V4 4.5.0 > > > Build the 4.5.0 release > Tasks: > Release Candidate > Upload to storage > Start Voting > Upload to Maven Central > Upload to release store > Update JavaDoc > Send Release Mail to announce mailing list -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1284) V4: Build 4.5.0 release
[ https://issues.apache.org/jira/browse/OLINGO-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz resolved OLINGO-1284. -- Resolution: Done > V4: Build 4.5.0 release > --- > > Key: OLINGO-1284 > URL: https://issues.apache.org/jira/browse/OLINGO-1284 > Project: Olingo > Issue Type: Task > Components: odata4-client, odata4-commons, odata4-ext, odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Christian Amend >Assignee: Christian Amend >Priority: Major > Fix For: (Java) V4 4.5.0 > > > Build the 4.5.0 release > Tasks: > Release Candidate > Upload to storage > Start Voting > Upload to Maven Central > Upload to release store > Update JavaDoc > Send Release Mail to announce mailing list -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1284) V4: Build 4.5.0 release
[ https://issues.apache.org/jira/browse/OLINGO-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1284: - Fix Version/s: (was: 4.6.0) (Java) V4 4.5.0 > V4: Build 4.5.0 release > --- > > Key: OLINGO-1284 > URL: https://issues.apache.org/jira/browse/OLINGO-1284 > Project: Olingo > Issue Type: Task > Components: odata4-client, odata4-commons, odata4-ext, odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Christian Amend >Assignee: Christian Amend >Priority: Major > Fix For: (Java) V4 4.5.0 > > > Build the 4.5.0 release > Tasks: > Release Candidate > Upload to storage > Start Voting > Upload to Maven Central > Upload to release store > Update JavaDoc > Send Release Mail to announce mailing list -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1284) V4: Build 4.5.0 release
[ https://issues.apache.org/jira/browse/OLINGO-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1284: - Fix Version/s: (was: (Java) V4 4.5.0) 4.6.0 > V4: Build 4.5.0 release > --- > > Key: OLINGO-1284 > URL: https://issues.apache.org/jira/browse/OLINGO-1284 > Project: Olingo > Issue Type: Task > Components: odata4-client, odata4-commons, odata4-ext, odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Christian Amend >Assignee: Christian Amend >Priority: Major > Fix For: 4.6.0 > > > Build the 4.5.0 release > Tasks: > Release Candidate > Upload to storage > Start Voting > Upload to Maven Central > Upload to release store > Update JavaDoc > Send Release Mail to announce mailing list -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-905) Support $all in server-core-ext framework
[ https://issues.apache.org/jira/browse/OLINGO-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-905: Fix Version/s: (was: (Java) V4 4.5.0) 4.6.0 > Support $all in server-core-ext framework > - > > Key: OLINGO-905 > URL: https://issues.apache.org/jira/browse/OLINGO-905 > Project: Olingo > Issue Type: Improvement > Components: odata4-server >Affects Versions: (Java) V4 4.1.0 >Reporter: Ramesh Reddy >Assignee: Ramesh Reddy >Priority: Major > Fix For: 4.6.0 > > > server-core-ext currently does not support $all option, at a minimum the > service should return a 501 not-implemented message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1306) Batch does not support binary media
[ https://issues.apache.org/jira/browse/OLINGO-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1306: - Fix Version/s: (was: (Java) V4 4.5.0) 4.6.0 > Batch does not support binary media > --- > > Key: OLINGO-1306 > URL: https://issues.apache.org/jira/browse/OLINGO-1306 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.4.0 >Reporter: Dmitri >Priority: Major > Fix For: 4.6.0 > > > Batch body part is converted from a stream to a string with UTF-8, but it > should be handled as byte array. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1267) Is it possible to generate deep insert response with navigation properties?
[
https://issues.apache.org/jira/browse/OLINGO-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-1267:
-
Fix Version/s: (was: (Java) V4 4.5.0)
4.6.0
> Is it possible to generate deep insert response with navigation properties?
> ---
>
> Key: OLINGO-1267
> URL: https://issues.apache.org/jira/browse/OLINGO-1267
> Project: Olingo
> Issue Type: Question
> Components: odata4-server
>Affects Versions: (Java) V4 4.4.0
> Environment: windows
>Reporter: Dattatray
>Priority: Major
> Fix For: 4.6.0
>
>
> *1]Following is metadata*
> xmlns="http://docs.oasis-open.org/odata/ns/edm;>
>
>
>
>
>
>
> ContainsTarget="true" />
>
>
>
>
>
>
>
>
> ContainsTarget="true" />
>
>
>
>
>
>
> **2] method[POST]=>
> [http://localhost:8085/MagicXpiOData/ChildEntityns.OData_1/Aentity*]*
> {
> "Id":1,
> "Name": "A",
> "B":[
> { "Id":1, "Name": "B" }
> ]
> }
> *3]Response of new entity creation(generated response contains only simple
> properties of entity)*
> { "@odata.context": "$metadata#Aentity", "Id": 1, "Name": "A" }
> *4]My question: Is it possible to generate response(Containing with
> navigation properties also) like following*
> {
> "@odata.context": "$metadata#Aentity",
> "Id": 1,
> "Name": "A",
> "B":[
> { "Id":1, "Name": "B" }
> ]
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OLINGO-1211) netty-all is not a bundle but its dependency adds extra import package to MANIFEST.MF in server-api module
[ https://issues.apache.org/jira/browse/OLINGO-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1211: - Fix Version/s: (was: (Java) V4 4.5.0) 4.6.0 > netty-all is not a bundle but its dependency adds extra import package to > MANIFEST.MF in server-api module > -- > > Key: OLINGO-1211 > URL: https://issues.apache.org/jira/browse/OLINGO-1211 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.5.0 >Reporter: Dmitri >Priority: Major > Fix For: 4.6.0 > > > MANIFEST.MF sample: > Import-Package: io.netty.handler.codec.http,... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-919) $count is not supported as last segment on Functions/Actions
[ https://issues.apache.org/jira/browse/OLINGO-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-919: Fix Version/s: (was: (Java) V4 4.5.0) 4.6.0 > $count is not supported as last segment on Functions/Actions > > > Key: OLINGO-919 > URL: https://issues.apache.org/jira/browse/OLINGO-919 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.1.0 >Reporter: Ramesh Reddy >Assignee: Christian Amend >Priority: Major > Fix For: 4.6.0 > > > See more details on OLINGO-915 > When function (including function imports) and action (and AI ) return > collection values, then that url can end with $count. For reference see [1] > [1] > http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part2-url-conventions/odata-v4.0-errata02-os-part2-url-conventions-complete.html#_Toc406398093 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1268) Olingo don't give error message like "The non-nullable property is missing" for navigationProperty
[
https://issues.apache.org/jira/browse/OLINGO-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-1268:
-
Fix Version/s: (was: (Java) V4 4.5.0)
4.6.0
> Olingo don't give error message like "The non-nullable property is missing"
> for navigationProperty
> --
>
> Key: OLINGO-1268
> URL: https://issues.apache.org/jira/browse/OLINGO-1268
> Project: Olingo
> Issue Type: Question
> Components: odata4-server
>Affects Versions: (Java) V4 4.4.0
>Reporter: Dattatray
>Priority: Major
> Fix For: 4.6.0
>
>
> *Olingo gives error message for non-nullable simple property of entity but
> not navigationProperty*
> **1]Following is metadata*
> xmlns="http://docs.oasis-open.org/odata/ns/edm;>
>
>
>
>
>
> Unicode="false" />
> ContainsTarget="true" />
>
>
>
>
>
>
>
> Unicode="false" />
> Nullable="false" ContainsTarget="true" />
>
>
>
>
>
>
> *2]Request[post]http://localhost:8085/MagicXpiOData/ChildEntityns.OData_1/Aentity*
> in the following body i don't given the "Name" property of entity A
> {
> "Id":1,
>
> "B":[{
> "Id":1,
> "Name": "B"
> }]
>
> }
> *3]Response(It gives error for missing property of entity A) *
> {
> "error": {
> "code": null,
> "message": "The non-nullable property 'Name' is missing."
> }
> }
> *4]Request[post]http://localhost:8085/MagicXpiOData/ChildEntityns.OData_1/Aentity*
> In following body i don't given the "Name" property of navigationProperty B
> {
> "Id":1,
> "Name": "A",
> "B":[{
> "Id":1
>
> }]
>
> }
> *5]Reseponse(but not given the error message for navigation property)*
> {
> "@odata.context": "$metadata#Aentity",
> "Id": 1,
> "Name": "A"
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OLINGO-1019) Navigation Links not explicitly added to entity are not shown in JSON "metadata=full" response
[ https://issues.apache.org/jira/browse/OLINGO-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1019: - Fix Version/s: (was: (Java) V4 4.5.0) 4.6.0 > Navigation Links not explicitly added to entity are not shown in JSON > "metadata=full" response > -- > > Key: OLINGO-1019 > URL: https://issues.apache.org/jira/browse/OLINGO-1019 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.2.0 >Reporter: Ashan Bakmeedeniya >Assignee: Ramesh Reddy >Priority: Major > Fix For: 4.6.0 > > Attachments: OLINGO-1019.patch > > > Navigation links not added to entity explicitly are not serialized in the > json response when client request "odata.metadata=full". > In ODataXmlSerializer even if navigation links are not explicitly added to > the entity, they are serialized to response. Hence, one would expect similar > behavior with ODataJsonSerializer as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1276) Client incorrectly parses stream with left brace in JSON string
[
https://issues.apache.org/jira/browse/OLINGO-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-1276:
-
Fix Version/s: (was: (Java) V4 4.5.0)
4.6.0
> Client incorrectly parses stream with left brace in JSON string
> ---
>
> Key: OLINGO-1276
> URL: https://issues.apache.org/jira/browse/OLINGO-1276
> Project: Olingo
> Issue Type: Bug
> Components: odata4-client
>Affects Versions: (Java) V4 4.4.0
>Reporter: Kristof Lievens
>Priority: Blocker
> Fix For: 4.6.0
>
> Attachments:
> 0001-fixes-issue-when-JSON-stream-contains-a-left-brace-i.patch
>
>
> When a JSON string contains a '{' character, the response stream is
> incorrectly parsed into OData entities by the
> org.apache.olingo.client.api.domain.ClientEntitySetIterator class.
> Please check the patch file in attachment with a fix for the issue.
> This bug has already been reported in February 2015, see
> [https://github.com/apache/olingo-odata4/pull/4.] I didn't notice the fix
> linked to this Github issue before I started coding my own fix, but it looks
> pretty similar.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OLINGO-1277) Olingo Java v2 JPA processor concurrency problems while building a query
[
https://issues.apache.org/jira/browse/OLINGO-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715001#comment-16715001
]
Michael Bolz commented on OLINGO-1277:
--
I have not deeply checked but I guess the root cause is here
{{org.apache.olingo.odata2.jpa.processor.api.ODataJPAServiceFactory}}.
The fields should not be class fields. Because parallel calls to
{{org.apache.olingo.odata2.jpa.processor.api.ODataJPAServiceFactory#createService}}
might result in concurrency problems.
Regards, Michael
> Olingo Java v2 JPA processor concurrency problems while building a query
>
>
> Key: OLINGO-1277
> URL: https://issues.apache.org/jira/browse/OLINGO-1277
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.10
>Reporter: Nikolay
>Assignee: Michael Bolz
>Priority: Major
> Attachments: olingo.png
>
>
> When querying simultaneously several filter queries similar to
> {endpoint}/Logs/$count?$filter=(level%20eq%20%27ERROR%27)%20and%20(timeStamp%20ge%20datetime%272018-07-13T08:15:52%27%20and%20timeStamp%20le%20datetime%272018-07-13T09:15:52%27)
>
> some of them fail due to concurrency problems - the query parameters get
> mixed to different JPA queries:
> org.hibernate.QueryException: Named parameter [1] not set
> at
> org.hibernate.query.internal.QueryParameterBindingsImpl.verifyParametersBound(QueryParameterBindingsImpl.java:251)
> at
> org.hibernate.query.internal.AbstractProducedQuery.beforeQuery(AbstractProducedQuery.java:1313)
> at
> org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1412)
> at org.hibernate.query.Query.getResultList(Query.java:146)
> at
> org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl.process(JPAProcessorImpl.java:233)
> java.lang.IllegalArgumentException: Unknown parameter position: 1
> at
> org.hibernate.query.internal.QueryParameterBindingsImpl.getBinding(QueryParameterBindingsImpl.java:240)
> at
> org.hibernate.query.internal.AbstractProducedQuery.setParameter(AbstractProducedQuery.java:503)
> at
> org.hibernate.query.internal.AbstractProducedQuery.setParameter(AbstractProducedQuery.java:104)
> at
> org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl.setPositionalParametersToQuery(JPAProcessorImpl.java:207)
> at
> org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl.process(JPAProcessorImpl.java:232)
>
> If the oDataJPAContext in JPAProcessorImpl is volatile, the problem doesn't
> occur any more.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OLINGO-1277) Olingo Java v2 JPA processor concurrency problems while building a query
[
https://issues.apache.org/jira/browse/OLINGO-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz reassigned OLINGO-1277:
Assignee: Michael Bolz
> Olingo Java v2 JPA processor concurrency problems while building a query
>
>
> Key: OLINGO-1277
> URL: https://issues.apache.org/jira/browse/OLINGO-1277
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.10
>Reporter: Nikolay
>Assignee: Michael Bolz
>Priority: Major
> Attachments: olingo.png
>
>
> When querying simultaneously several filter queries similar to
> {endpoint}/Logs/$count?$filter=(level%20eq%20%27ERROR%27)%20and%20(timeStamp%20ge%20datetime%272018-07-13T08:15:52%27%20and%20timeStamp%20le%20datetime%272018-07-13T09:15:52%27)
>
> some of them fail due to concurrency problems - the query parameters get
> mixed to different JPA queries:
> org.hibernate.QueryException: Named parameter [1] not set
> at
> org.hibernate.query.internal.QueryParameterBindingsImpl.verifyParametersBound(QueryParameterBindingsImpl.java:251)
> at
> org.hibernate.query.internal.AbstractProducedQuery.beforeQuery(AbstractProducedQuery.java:1313)
> at
> org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1412)
> at org.hibernate.query.Query.getResultList(Query.java:146)
> at
> org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl.process(JPAProcessorImpl.java:233)
> java.lang.IllegalArgumentException: Unknown parameter position: 1
> at
> org.hibernate.query.internal.QueryParameterBindingsImpl.getBinding(QueryParameterBindingsImpl.java:240)
> at
> org.hibernate.query.internal.AbstractProducedQuery.setParameter(AbstractProducedQuery.java:503)
> at
> org.hibernate.query.internal.AbstractProducedQuery.setParameter(AbstractProducedQuery.java:104)
> at
> org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl.setPositionalParametersToQuery(JPAProcessorImpl.java:207)
> at
> org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl.process(JPAProcessorImpl.java:232)
>
> If the oDataJPAContext in JPAProcessorImpl is volatile, the problem doesn't
> occur any more.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OLINGO-1301) In Spring Boot application is impossible to redefine Metadata with mapping model XML
[ https://issues.apache.org/jira/browse/OLINGO-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652273#comment-16652273 ] Michael Bolz edited comment on OLINGO-1301 at 10/16/18 7:11 PM: Merged with [this commit|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=d32a900a45e77ae41eeb6962755cda0e6452d3be]. was (Author: mirbo): Merged with [this commit| https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=d32a900a45e77ae41eeb6962755cda0e6452d3be] > In Spring Boot application is impossible to redefine Metadata with mapping > model XML > -- > > Key: OLINGO-1301 > URL: https://issues.apache.org/jira/browse/OLINGO-1301 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.10 >Reporter: Sergey Chebotarev >Assignee: Michael Bolz >Priority: Major > Fix For: V2 2.0.11 > > Attachments: 1. bash 2018-10-16 09-39-58.png, patch.diff, patch.diff, > screen.png > > > In Spring Boot application is impossible to redefine Metadata with mapping > model XML. Application have not access by Mapping model XML form resource > directory. Hard coded prefix ''../../" does not allow access to the file. > See attachment. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1301) In Spring Boot application is impossible to redefine Metadata with mapping model XML
[ https://issues.apache.org/jira/browse/OLINGO-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz resolved OLINGO-1301. -- Resolution: Fixed Fix Version/s: V2 2.0.11 Merged with [this commit| https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=d32a900a45e77ae41eeb6962755cda0e6452d3be] > In Spring Boot application is impossible to redefine Metadata with mapping > model XML > -- > > Key: OLINGO-1301 > URL: https://issues.apache.org/jira/browse/OLINGO-1301 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.10 >Reporter: Sergey Chebotarev >Assignee: Michael Bolz >Priority: Major > Fix For: V2 2.0.11 > > Attachments: 1. bash 2018-10-16 09-39-58.png, patch.diff, patch.diff, > screen.png > > > In Spring Boot application is impossible to redefine Metadata with mapping > model XML. Application have not access by Mapping model XML form resource > directory. Hard coded prefix ''../../" does not allow access to the file. > See attachment. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1301) In Spring Boot application is impossible to redefine Metadata with mapping model XML
[
https://issues.apache.org/jira/browse/OLINGO-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652264#comment-16652264
]
Michael Bolz commented on OLINGO-1301:
--
Hi [~chebotarev_sa],
Sorry I missed to run the {{build.quality}} profile before my commit.
Now it should be fine and I will merge the change into the master.
Thanks again for the contribution ;o)
Kind Regards, Michael
> In Spring Boot application is impossible to redefine Metadata with mapping
> model XML
> --
>
> Key: OLINGO-1301
> URL: https://issues.apache.org/jira/browse/OLINGO-1301
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.10
>Reporter: Sergey Chebotarev
>Assignee: Michael Bolz
>Priority: Major
> Attachments: 1. bash 2018-10-16 09-39-58.png, patch.diff, patch.diff,
> screen.png
>
>
> In Spring Boot application is impossible to redefine Metadata with mapping
> model XML. Application have not access by Mapping model XML form resource
> directory. Hard coded prefix ''../../" does not allow access to the file.
> See attachment.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OLINGO-1301) In Spring Boot application is impossible to redefine Metadata with mapping model XML
[ https://issues.apache.org/jira/browse/OLINGO-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650725#comment-16650725 ] Michael Bolz commented on OLINGO-1301: -- Hi [~chebotarev_sa], I take your patch and changed it slightly. See Brach [OLINGO-1301|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=shortlog;h=refs/heads/OLINGO-1301]. If this is fine for you I will merge it into the master. Kind Regards, Michael > In Spring Boot application is impossible to redefine Metadata with mapping > model XML > -- > > Key: OLINGO-1301 > URL: https://issues.apache.org/jira/browse/OLINGO-1301 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.10 >Reporter: Sergey Chebotarev >Assignee: Michael Bolz >Priority: Major > Attachments: patch.diff, screen.png > > > In Spring Boot application is impossible to redefine Metadata with mapping > model XML. Application have not access by Mapping model XML form resource > directory. Hard coded prefix ''../../" does not allow access to the file. > See attachment. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1301) In Spring Boot application is impossible to redefine Metadata with mapping model XML
[ https://issues.apache.org/jira/browse/OLINGO-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639264#comment-16639264 ] Michael Bolz commented on OLINGO-1301: -- Hi [~chebotarev_sa], Thanks for the contribution. I will take a look into and give you feedback (and/or merge it). Kind Regards, Michael > In Spring Boot application is impossible to redefine Metadata with mapping > model XML > -- > > Key: OLINGO-1301 > URL: https://issues.apache.org/jira/browse/OLINGO-1301 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.10 >Reporter: Sergey Chebotarev >Assignee: Michael Bolz >Priority: Major > Attachments: patch.diff, screen.png > > > In Spring Boot application is impossible to redefine Metadata with mapping > model XML. Application have not access by Mapping model XML form resource > directory. Hard coded prefix ''../../" does not allow access to the file. > See attachment. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OLINGO-1301) In Spring Boot application is impossible to redefine Metadata with mapping model XML
[ https://issues.apache.org/jira/browse/OLINGO-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz reassigned OLINGO-1301: Assignee: Michael Bolz > In Spring Boot application is impossible to redefine Metadata with mapping > model XML > -- > > Key: OLINGO-1301 > URL: https://issues.apache.org/jira/browse/OLINGO-1301 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.10 >Reporter: Sergey Chebotarev >Assignee: Michael Bolz >Priority: Major > Attachments: patch.diff, screen.png > > > In Spring Boot application is impossible to redefine Metadata with mapping > model XML. Application have not access by Mapping model XML form resource > directory. Hard coded prefix ''../../" does not allow access to the file. > See attachment. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OLINGO-562) Spring support for Olingo v4 server
[ https://issues.apache.org/jira/browse/OLINGO-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz closed OLINGO-562. --- Resolution: Won't Fix Hi, because the issue is older then two years and affected version was beta is set I will close this. For the case that someone has the same issue with current version please reopen. Regards, Michael > Spring support for Olingo v4 server > --- > > Key: OLINGO-562 > URL: https://issues.apache.org/jira/browse/OLINGO-562 > Project: Olingo > Issue Type: New Feature >Affects Versions: (Java) V4 4.0.0-beta-02 > Environment: Java, Spring 4 >Reporter: Thierry Templier >Assignee: Michael Bolz > Attachments: > 0001-OLINGO-562-split-the-code-between-the-generic-part-a.patch, > olingo-server-v4-spring-20150311.zip > > > Hello, > I have implemented a Spring support for Olingo v4 server side. It allows to > define declaratively within your Spring configuration: > * EDM provider (see file > src/test/resources/applicationContext-edm-provider-namespace.xml) > * HTTP handler > (src/test/resources/applicationContext-http-handler-namespace.xml) > A dedicated servlet is provided to get an instance of ODataHttpHandler from a > Spring container and use it to handle request. > You can find enclosed the corresponding code. > I don't how such code can be integrated to Olingo. I think that it > corresponds more to an extension than something to put in the Olingo core. > Feel free to give me your feedback. > Thierry -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OLINGO-605) Olingo should support custom types e.g. Geometry by using XmlAdapter from JaxB
[
https://issues.apache.org/jira/browse/OLINGO-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-605:
Fix Version/s: V2 2.0.10
> Olingo should support custom types e.g. Geometry by using XmlAdapter from JaxB
> --
>
> Key: OLINGO-605
> URL: https://issues.apache.org/jira/browse/OLINGO-605
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-jpa
>Affects Versions: V2 2.0.3
>Reporter: Manuel Blechschmidt
>Assignee: Michael Bolz
>Priority: Minor
> Labels: GIS, custom, spatial, types
> Fix For: V2 2.0.10
>
>
> I am currently developing a software where I save GIS coordinates as part of
> my entities. I want to send these geometries as a string through OData to a
> client.
> Technically I do the following:
> OpenGis -> Hibernate Spatial -> JPA -> Olingo -> JavaScript -> OpenLayers
> I already have an XmlAdapter that maps my Geometry to WKT. I want to use this
> as well for Olingo serialization
> I copied the following file in my workspace and extended the
> convertToEdmSimpleType function:
> org.apache.olingo.odata2.jpa.processor.core.access.model.JPATypeConvertor
> {code:java}
> public static EdmSimpleTypeKind
> ...
> } else if(jpaType.equals(Geometry.class)) {
> // "OData - JPA Type Converter: Type [class
> com.vividsolutions.jts.geom.Geometry] not supported"
> return EdmSimpleTypeKind.String;
> }
> throw
> ODataJPAModelException.throwException(ODataJPAModelException.TYPE_NOT_SUPPORTED
> .addContent(jpaType.toString()), null);
> }
> {code}
> This is quick and dirty and it would be nice if there would be a cleaner
> solution to do so.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OLINGO-605) Olingo should support custom types e.g. Geometry by using XmlAdapter from JaxB
[
https://issues.apache.org/jira/browse/OLINGO-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz resolved OLINGO-605.
-
Resolution: Fixed
> Olingo should support custom types e.g. Geometry by using XmlAdapter from JaxB
> --
>
> Key: OLINGO-605
> URL: https://issues.apache.org/jira/browse/OLINGO-605
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-jpa
>Affects Versions: V2 2.0.3
>Reporter: Manuel Blechschmidt
>Assignee: Michael Bolz
>Priority: Minor
> Labels: GIS, custom, spatial, types
>
> I am currently developing a software where I save GIS coordinates as part of
> my entities. I want to send these geometries as a string through OData to a
> client.
> Technically I do the following:
> OpenGis -> Hibernate Spatial -> JPA -> Olingo -> JavaScript -> OpenLayers
> I already have an XmlAdapter that maps my Geometry to WKT. I want to use this
> as well for Olingo serialization
> I copied the following file in my workspace and extended the
> convertToEdmSimpleType function:
> org.apache.olingo.odata2.jpa.processor.core.access.model.JPATypeConvertor
> {code:java}
> public static EdmSimpleTypeKind
> ...
> } else if(jpaType.equals(Geometry.class)) {
> // "OData - JPA Type Converter: Type [class
> com.vividsolutions.jts.geom.Geometry] not supported"
> return EdmSimpleTypeKind.String;
> }
> throw
> ODataJPAModelException.throwException(ODataJPAModelException.TYPE_NOT_SUPPORTED
> .addContent(jpaType.toString()), null);
> }
> {code}
> This is quick and dirty and it would be nice if there would be a cleaner
> solution to do so.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OLINGO-605) Olingo should support custom types e.g. Geometry by using XmlAdapter from JaxB
[
https://issues.apache.org/jira/browse/OLINGO-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188010#comment-16188010
]
Michael Bolz commented on OLINGO-605:
-
Hi [~manuel_b]
Thanks for the feature (see: https://github.com/apache/olingo-odata2/pull/4).
Based on this I updated the master (with minor changes to your pull request),
see [commit
7aac7976|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=7aac7976b3d576f3f24c8c0f4d75e0c7b1e96f95].
Again Thanks for the contribution.
Kind Regards, Michael
> Olingo should support custom types e.g. Geometry by using XmlAdapter from JaxB
> --
>
> Key: OLINGO-605
> URL: https://issues.apache.org/jira/browse/OLINGO-605
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-jpa
>Affects Versions: V2 2.0.3
>Reporter: Manuel Blechschmidt
>Assignee: Michael Bolz
>Priority: Minor
> Labels: GIS, custom, spatial, types
>
> I am currently developing a software where I save GIS coordinates as part of
> my entities. I want to send these geometries as a string through OData to a
> client.
> Technically I do the following:
> OpenGis -> Hibernate Spatial -> JPA -> Olingo -> JavaScript -> OpenLayers
> I already have an XmlAdapter that maps my Geometry to WKT. I want to use this
> as well for Olingo serialization
> I copied the following file in my workspace and extended the
> convertToEdmSimpleType function:
> org.apache.olingo.odata2.jpa.processor.core.access.model.JPATypeConvertor
> {code:java}
> public static EdmSimpleTypeKind
> ...
> } else if(jpaType.equals(Geometry.class)) {
> // "OData - JPA Type Converter: Type [class
> com.vividsolutions.jts.geom.Geometry] not supported"
> return EdmSimpleTypeKind.String;
> }
> throw
> ODataJPAModelException.throwException(ODataJPAModelException.TYPE_NOT_SUPPORTED
> .addContent(jpaType.toString()), null);
> }
> {code}
> This is quick and dirty and it would be nice if there would be a cleaner
> solution to do so.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (OLINGO-605) Olingo should support custom types e.g. Geometry by using XmlAdapter from JaxB
[
https://issues.apache.org/jira/browse/OLINGO-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz reassigned OLINGO-605:
---
Assignee: Michael Bolz
> Olingo should support custom types e.g. Geometry by using XmlAdapter from JaxB
> --
>
> Key: OLINGO-605
> URL: https://issues.apache.org/jira/browse/OLINGO-605
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-jpa
>Affects Versions: V2 2.0.3
>Reporter: Manuel Blechschmidt
>Assignee: Michael Bolz
>Priority: Minor
> Labels: GIS, custom, spatial, types
>
> I am currently developing a software where I save GIS coordinates as part of
> my entities. I want to send these geometries as a string through OData to a
> client.
> Technically I do the following:
> OpenGis -> Hibernate Spatial -> JPA -> Olingo -> JavaScript -> OpenLayers
> I already have an XmlAdapter that maps my Geometry to WKT. I want to use this
> as well for Olingo serialization
> I copied the following file in my workspace and extended the
> convertToEdmSimpleType function:
> org.apache.olingo.odata2.jpa.processor.core.access.model.JPATypeConvertor
> {code:java}
> public static EdmSimpleTypeKind
> ...
> } else if(jpaType.equals(Geometry.class)) {
> // "OData - JPA Type Converter: Type [class
> com.vividsolutions.jts.geom.Geometry] not supported"
> return EdmSimpleTypeKind.String;
> }
> throw
> ODataJPAModelException.throwException(ODataJPAModelException.TYPE_NOT_SUPPORTED
> .addContent(jpaType.toString()), null);
> }
> {code}
> This is quick and dirty and it would be nice if there would be a cleaner
> solution to do so.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OLINGO-996) ODataJPA Extension creates illegal Entity Container Name
[
https://issues.apache.org/jira/browse/OLINGO-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-996:
Fix Version/s: V2 2.0.10
> ODataJPA Extension creates illegal Entity Container Name
>
>
> Key: OLINGO-996
> URL: https://issues.apache.org/jira/browse/OLINGO-996
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Reporter: Tobias Stolzenberger
>Assignee: Michael Bolz
>Priority: Minor
> Fix For: V2 2.0.10
>
>
> Hi,
> I'm using the Olingo JPA extension. The persistence unit I'm using has a name
> containing dots:
> like this:
> {code:borderStyle=solid}
>
> {code}
> Per default the JPA extension uses the name of the persistence as name of the
> entity container.
> The problem is that per OData spec the entity container name must names
> containing dots:
>
> https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MC-CSDL/[MC-CSDL].pdf
>
> Page 31: "EntityContainer MUST have a Name attribute defined that is of type
> SimpleIdentifier".
> I found a workaround to overwrite the entity container name in code. However
> I think it makes sense that the default algorithm to automatically create
> this name should produce only valid names.
> Regards,
> Tobias
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OLINGO-996) ODataJPA Extension creates illegal Entity Container Name
[
https://issues.apache.org/jira/browse/OLINGO-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz resolved OLINGO-996.
-
Resolution: Fixed
> ODataJPA Extension creates illegal Entity Container Name
>
>
> Key: OLINGO-996
> URL: https://issues.apache.org/jira/browse/OLINGO-996
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Reporter: Tobias Stolzenberger
>Assignee: Michael Bolz
>Priority: Minor
> Fix For: V2 2.0.10
>
>
> Hi,
> I'm using the Olingo JPA extension. The persistence unit I'm using has a name
> containing dots:
> like this:
> {code:borderStyle=solid}
>
> {code}
> Per default the JPA extension uses the name of the persistence as name of the
> entity container.
> The problem is that per OData spec the entity container name must names
> containing dots:
>
> https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MC-CSDL/[MC-CSDL].pdf
>
> Page 31: "EntityContainer MUST have a Name attribute defined that is of type
> SimpleIdentifier".
> I found a workaround to overwrite the entity container name in code. However
> I think it makes sense that the default algorithm to automatically create
> this name should produce only valid names.
> Regards,
> Tobias
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OLINGO-996) ODataJPA Extension creates illegal Entity Container Name
[
https://issues.apache.org/jira/browse/OLINGO-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz closed OLINGO-996.
---
> ODataJPA Extension creates illegal Entity Container Name
>
>
> Key: OLINGO-996
> URL: https://issues.apache.org/jira/browse/OLINGO-996
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Reporter: Tobias Stolzenberger
>Assignee: Michael Bolz
>Priority: Minor
> Fix For: V2 2.0.10
>
>
> Hi,
> I'm using the Olingo JPA extension. The persistence unit I'm using has a name
> containing dots:
> like this:
> {code:borderStyle=solid}
>
> {code}
> Per default the JPA extension uses the name of the persistence as name of the
> entity container.
> The problem is that per OData spec the entity container name must names
> containing dots:
>
> https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MC-CSDL/[MC-CSDL].pdf
>
> Page 31: "EntityContainer MUST have a Name attribute defined that is of type
> SimpleIdentifier".
> I found a workaround to overwrite the entity container name in code. However
> I think it makes sense that the default algorithm to automatically create
> this name should produce only valid names.
> Regards,
> Tobias
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OLINGO-996) ODataJPA Extension creates illegal Entity Container Name
[
https://issues.apache.org/jira/browse/OLINGO-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187046#comment-16187046
]
Michael Bolz commented on OLINGO-996:
-
Hi [~tobias.stolzenberger],
Thanks for the hint.
Further specs:
- https://msdn.microsoft.com/en-us/library/bb387135(v=vs.100).aspx
- http://www.fileformat.info/info/unicode/char/2e/index.htm
Fixed with commit
[751e316d|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=751e316da5899700575d4126b00f45fce8850c50].
Regards, Michael
> ODataJPA Extension creates illegal Entity Container Name
>
>
> Key: OLINGO-996
> URL: https://issues.apache.org/jira/browse/OLINGO-996
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Reporter: Tobias Stolzenberger
>Assignee: Michael Bolz
>Priority: Minor
>
> Hi,
> I'm using the Olingo JPA extension. The persistence unit I'm using has a name
> containing dots:
> like this:
> {code:borderStyle=solid}
>
> {code}
> Per default the JPA extension uses the name of the persistence as name of the
> entity container.
> The problem is that per OData spec the entity container name must names
> containing dots:
>
> https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MC-CSDL/[MC-CSDL].pdf
>
> Page 31: "EntityContainer MUST have a Name attribute defined that is of type
> SimpleIdentifier".
> I found a workaround to overwrite the entity container name in code. However
> I think it makes sense that the default algorithm to automatically create
> this name should produce only valid names.
> Regards,
> Tobias
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OLINGO-561) Client proxy fails updating entity nullifying a nullable property
[ https://issues.apache.org/jira/browse/OLINGO-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz closed OLINGO-561. --- Resolution: Cannot Reproduce Hi, because the issue is older then two years and affected version was beta is set I will close this. For the case that someone has the same issue with current version please reopen. Regards, Michael > Client proxy fails updating entity nullifying a nullable property > - > > Key: OLINGO-561 > URL: https://issues.apache.org/jira/browse/OLINGO-561 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.0.0-beta-02 >Reporter: fabio martelli > > Currently the client proxy generates a patch request to nullify a specific > entity property. The patch body sent to the server is an entity type > including element like as following. > firstn...@odata.type":"String","FirstName":null > This seems to generate failures in case of non-string properties. > Furthermore, I'm not sure about the correctness of using patch requests to > nullify properties. It would be better to manage property nullifications via > a specific DELETE request per property to be nullified. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OLINGO-470) V3 OData client needs to support creating relationships using $links
[ https://issues.apache.org/jira/browse/OLINGO-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz closed OLINGO-470. --- Resolution: Won't Fix Hi, because the issue is older then two years and affected version was beta is set I will close this. For the case that someone has the same issue with current version please reopen. Regards, Michael > V3 OData client needs to support creating relationships using $links > > > Key: OLINGO-470 > URL: https://issues.apache.org/jira/browse/OLINGO-470 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.0.0-beta-01 >Reporter: Mark Sztainbok > > Currently Olingo does not allow for relationships to be created via $link > URLs (OData V3 Spec section 10.2.4) when using the client. This required > though as is commonly used to establish relationships between entities in an > OData API (e.g. http://msdn.microsoft.com/en-us/library/azure/dn151600.aspx > and http://msdn.microsoft.com/en-us/library/azure/dn151607.aspx) > WCF Data Services Client supports adding relationships via the AddLink method > (http://msdn.microsoft.com/en-us/library/system.data.services.client.dataservicecontext.addlink(v=vs.103).aspx) > for 1 to many and many to many relationships and SetLink > (http://msdn.microsoft.com/en-us/library/system.data.services.client.dataservicecontext.setlink(v=vs.103).aspx) > method for 1:1 relationships and DeleteLink to remove a link > (http://msdn.microsoft.com/en-us/library/system.data.services.client.dataservicecontext.deletelink(v=vs.103).aspx) > Olingo needs to have some similar functionality. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OLINGO-638) Many to many relationship not working both ways
[ https://issues.apache.org/jira/browse/OLINGO-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz closed OLINGO-638. --- Resolution: Cannot Reproduce Assignee: Michael Bolz Hi, because the issue is older then two years and no affected version is set I will close this. For the case that someone has the same issue please reopen and please provide more detailed information about the bug. Regards, Michael > Many to many relationship not working both ways > --- > > Key: OLINGO-638 > URL: https://issues.apache.org/jira/browse/OLINGO-638 > Project: Olingo > Issue Type: Bug >Reporter: Adith Shenoy >Assignee: Michael Bolz > > Hi > I have 2 entities A and B linked via the Jointable E. > When i am creating A, i explicitly link the entity B to the entity A using > "__metadata". > Now If i use the navigation from A to fetch the related B entities, i am > getting the details, however if i am using the navigation from B to get > related A entities, it is not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OLINGO-996) ODataJPA Extension creates illegal Entity Container Name
[
https://issues.apache.org/jira/browse/OLINGO-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz reassigned OLINGO-996:
---
Assignee: Michael Bolz
> ODataJPA Extension creates illegal Entity Container Name
>
>
> Key: OLINGO-996
> URL: https://issues.apache.org/jira/browse/OLINGO-996
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Reporter: Tobias Stolzenberger
>Assignee: Michael Bolz
>Priority: Minor
>
> Hi,
> I'm using the Olingo JPA extension. The persistence unit I'm using has a name
> containing dots:
> like this:
> {code:borderStyle=solid}
>
> {code}
> Per default the JPA extension uses the name of the persistence as name of the
> entity container.
> The problem is that per OData spec the entity container name must names
> containing dots:
>
> https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MC-CSDL/[MC-CSDL].pdf
>
> Page 31: "EntityContainer MUST have a Name attribute defined that is of type
> SimpleIdentifier".
> I found a workaround to overwrite the entity container name in code. However
> I think it makes sense that the default algorithm to automatically create
> this name should produce only valid names.
> Regards,
> Tobias
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OLINGO-1146) CLONE - Cannot Filter on Navigation Property
[ https://issues.apache.org/jira/browse/OLINGO-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz resolved OLINGO-1146. -- Resolution: Fixed Fix Version/s: (was: V2 2.0.8) V2 2.0.10 > CLONE - Cannot Filter on Navigation Property > > > Key: OLINGO-1146 > URL: https://issues.apache.org/jira/browse/OLINGO-1146 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.0 >Reporter: igor nemtsov >Assignee: Michael Bolz > Fix For: V2 2.0.10 > > Attachments: olingo-414-exception.diff, olingo-414-patch.diff, > olingo-odata2-parent.patch > > > We are receiving an error when we try to filter on a navigation property. In > our solution we have a Notification entity and a User entity, we would like > to retrieve a specific Notification but only if it is linked to the > requesting user. This would involve an ODATA request which filters on both > the UserId and the NotificationId. An example of the URL we are invoking is: > dspplatform.svc/Notifications?$filter=NotificationId%20eq%204%20and%20UserDetails/UserId%20eq%202 > This returns the following error: > org.apache.olingo.odata2.core.edm.provider.EdmNavigationPropertyImplProv > cannot be cast to org.apache.olingo.odata2.api.edm.EdmProperty > Can you please advise on how to perform filters on a Navigation property as > we need this as part of our core functionality? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OLINGO-1146) CLONE - Cannot Filter on Navigation Property
[ https://issues.apache.org/jira/browse/OLINGO-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177948#comment-16177948 ] Michael Bolz commented on OLINGO-1146: -- Hi all, I changed the filter parsing that only the last property is checked regarding invalid multiplicity (see [this commit|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=6ce2421a5d7ebb40d6456d12f38913f725e87457]). Accordingly the filter on navigation now works again (however I have to admit that for the JPA extension we need a lot more tests). For the case that filter on navigation property still do not work, please reopen and give detailed feedback. Regards, Michael > CLONE - Cannot Filter on Navigation Property > > > Key: OLINGO-1146 > URL: https://issues.apache.org/jira/browse/OLINGO-1146 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.0 >Reporter: igor nemtsov >Assignee: Michael Bolz > Fix For: V2 2.0.10 > > Attachments: olingo-414-exception.diff, olingo-414-patch.diff, > olingo-odata2-parent.patch > > > We are receiving an error when we try to filter on a navigation property. In > our solution we have a Notification entity and a User entity, we would like > to retrieve a specific Notification but only if it is linked to the > requesting user. This would involve an ODATA request which filters on both > the UserId and the NotificationId. An example of the URL we are invoking is: > dspplatform.svc/Notifications?$filter=NotificationId%20eq%204%20and%20UserDetails/UserId%20eq%202 > This returns the following error: > org.apache.olingo.odata2.core.edm.provider.EdmNavigationPropertyImplProv > cannot be cast to org.apache.olingo.odata2.api.edm.EdmProperty > Can you please advise on how to perform filters on a Navigation property as > we need this as part of our core functionality? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OLINGO-1146) CLONE - Cannot Filter on Navigation Property
[
https://issues.apache.org/jira/browse/OLINGO-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177790#comment-16177790
]
Michael Bolz commented on OLINGO-1146:
--
The problem seems to be a to strict check in filter parsing:
{{org/apache/olingo/odata2/core/uri/expression/FilterParserImpl.java:509}}
When the new code for to many check is commented out all works as before:
{code}
if (edmProperty != null) {
property.setEdmProperty(edmProperty);
property.setEdmType(edmProperty.getType());
//if (edmProperty.getMultiplicity() == EdmMultiplicity.MANY) {
// throw new ExpressionParserException(
// ExpressionParserException.INVALID_MULTIPLICITY.create()
// .addContent(propertyName)
// .addContent(propertyToken.getPosition() + 1));
//}
} else {
{code}
Currently I guess the filter must be adapted that only the last part of a
filter literal is checked for multiplicity (e.g. "delivered" of
"SalesOrderLineItemDetails/delivered eq true").
But this must be checked.
Regards, Michael
> CLONE - Cannot Filter on Navigation Property
>
>
> Key: OLINGO-1146
> URL: https://issues.apache.org/jira/browse/OLINGO-1146
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.0
>Reporter: igor nemtsov
>Assignee: Michael Bolz
> Fix For: V2 2.0.8
>
> Attachments: olingo-414-exception.diff, olingo-414-patch.diff,
> olingo-odata2-parent.patch
>
>
> We are receiving an error when we try to filter on a navigation property. In
> our solution we have a Notification entity and a User entity, we would like
> to retrieve a specific Notification but only if it is linked to the
> requesting user. This would involve an ODATA request which filters on both
> the UserId and the NotificationId. An example of the URL we are invoking is:
> dspplatform.svc/Notifications?$filter=NotificationId%20eq%204%20and%20UserDetails/UserId%20eq%202
> This returns the following error:
> org.apache.olingo.odata2.core.edm.provider.EdmNavigationPropertyImplProv
> cannot be cast to org.apache.olingo.odata2.api.edm.EdmProperty
> Can you please advise on how to perform filters on a Navigation property as
> we need this as part of our core functionality?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OLINGO-1146) CLONE - Cannot Filter on Navigation Property
[
https://issues.apache.org/jira/browse/OLINGO-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177783#comment-16177783
]
Michael Bolz commented on OLINGO-1146:
--
Hi all,
I just take a short look into this issue and it seems that there was a
regression introduced.
Currently I guess during fix of OLINGO-1026.
At least with the fix for OLINGO-414 (commit {{07984dc1}}) it has worked.
(RefScenario with URL
http://localhost:8080/SalesOrderProcessing.svc/SalesOrders?$filter=SalesOrderLineItemDetails/delivered%20eq%20true).
I will check and give feedback.
Regards, Michael
> CLONE - Cannot Filter on Navigation Property
>
>
> Key: OLINGO-1146
> URL: https://issues.apache.org/jira/browse/OLINGO-1146
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.0
>Reporter: igor nemtsov
>Assignee: Michael Bolz
> Fix For: V2 2.0.8
>
> Attachments: olingo-414-exception.diff, olingo-414-patch.diff,
> olingo-odata2-parent.patch
>
>
> We are receiving an error when we try to filter on a navigation property. In
> our solution we have a Notification entity and a User entity, we would like
> to retrieve a specific Notification but only if it is linked to the
> requesting user. This would involve an ODATA request which filters on both
> the UserId and the NotificationId. An example of the URL we are invoking is:
> dspplatform.svc/Notifications?$filter=NotificationId%20eq%204%20and%20UserDetails/UserId%20eq%202
> This returns the following error:
> org.apache.olingo.odata2.core.edm.provider.EdmNavigationPropertyImplProv
> cannot be cast to org.apache.olingo.odata2.api.edm.EdmProperty
> Can you please advise on how to perform filters on a Navigation property as
> we need this as part of our core functionality?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (OLINGO-1156) ODataJPAServiceFactory - Cannot create or update entry with ManyToOne association
[ https://issues.apache.org/jira/browse/OLINGO-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177757#comment-16177757 ] Michael Bolz edited comment on OLINGO-1156 at 9/23/17 12:03 PM: Hi all, Just for clarification. You do a e.g. a POST request for "Alternative" wich includes "Scopes" (as expanded entity) wich should be also created. Correct? Can you please also provide the sample request payload? Regards, Michael was (Author: mirbo): Hi all, Just for clarification. You do a e.g. a POST request for "Atlernative" wich includes "Scopes" (as expanded entity) wich should be also created. Correct? Can you please also provide the sample request payload? Regards, Michael > ODataJPAServiceFactory - Cannot create or update entry with ManyToOne > association > - > > Key: OLINGO-1156 > URL: https://issues.apache.org/jira/browse/OLINGO-1156 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.9 > Environment: EclipseLink 2.5.2 >Reporter: Tilo Eilebrecht >Assignee: Michael Bolz >Priority: Blocker > Attachments: Alternative.java, Scope.java > > > My project uses ODataJPAServiceFactory as described in the tutorial for JPA. > I have an entity which references another entity with a ManyToOne > relationship. If I submit a create or change request, the reference > (idAlternative) is not created or updated. As the field is not nullable, > object creation fails altogether. > See my Entities in the attachment. The JoinColumn is idAlternative. > I have investigated into possible causes and I stumbled on > org.apache.olingo.odata2.jpa.processor.core.access.dataJPAEntity, method > write. This method identifies idAlternative as an embeddable key and removes > it from the propertyNames set. Therefore it does not get written into the > object. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OLINGO-1156) ODataJPAServiceFactory - Cannot create or update entry with ManyToOne association
[ https://issues.apache.org/jira/browse/OLINGO-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177757#comment-16177757 ] Michael Bolz commented on OLINGO-1156: -- Hi all, Just for clarification. You do a e.g. a POST request for "Atlernative" wich includes "Scopes" (as expanded entity) wich should be also created. Correct? Can you please also provide the sample request payload? Regards, Michael > ODataJPAServiceFactory - Cannot create or update entry with ManyToOne > association > - > > Key: OLINGO-1156 > URL: https://issues.apache.org/jira/browse/OLINGO-1156 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.9 > Environment: EclipseLink 2.5.2 >Reporter: Tilo Eilebrecht >Assignee: Michael Bolz >Priority: Blocker > Attachments: Alternative.java, Scope.java > > > My project uses ODataJPAServiceFactory as described in the tutorial for JPA. > I have an entity which references another entity with a ManyToOne > relationship. If I submit a create or change request, the reference > (idAlternative) is not created or updated. As the field is not nullable, > object creation fails altogether. > See my Entities in the attachment. The JoinColumn is idAlternative. > I have investigated into possible causes and I stumbled on > org.apache.olingo.odata2.jpa.processor.core.access.dataJPAEntity, method > write. This method identifies idAlternative as an embeddable key and removes > it from the propertyNames set. Therefore it does not get written into the > object. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OLINGO-1156) ODataJPAServiceFactory - Cannot create or update entry with ManyToOne association
[ https://issues.apache.org/jira/browse/OLINGO-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz reassigned OLINGO-1156: Assignee: Michael Bolz > ODataJPAServiceFactory - Cannot create or update entry with ManyToOne > association > - > > Key: OLINGO-1156 > URL: https://issues.apache.org/jira/browse/OLINGO-1156 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.9 > Environment: EclipseLink 2.5.2 >Reporter: Tilo Eilebrecht >Assignee: Michael Bolz >Priority: Blocker > Attachments: Alternative.java, Scope.java > > > My project uses ODataJPAServiceFactory as described in the tutorial for JPA. > I have an entity which references another entity with a ManyToOne > relationship. If I submit a create or change request, the reference > (idAlternative) is not created or updated. As the field is not nullable, > object creation fails altogether. > See my Entities in the attachment. The JoinColumn is idAlternative. > I have investigated into possible causes and I stumbled on > org.apache.olingo.odata2.jpa.processor.core.access.dataJPAEntity, method > write. This method identifies idAlternative as an embeddable key and removes > it from the propertyNames set. Therefore it does not get written into the > object. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OLINGO-752) Add support for "+" sign as a separator in addition to %20 for URLs
[ https://issues.apache.org/jira/browse/OLINGO-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz closed OLINGO-752. --- > Add support for "+" sign as a separator in addition to %20 for URLs > --- > > Key: OLINGO-752 > URL: https://issues.apache.org/jira/browse/OLINGO-752 > Project: Olingo > Issue Type: New Feature > Components: odata2-core >Affects Versions: V2 2.0.4, (Java) V4 4.0.0-beta-03 >Reporter: Ronny Bremer >Priority: Minor > Attachments: 0002-OLINGO-752-Treat-as-space-in-Decoder.patch > > > Some well-known OData client libraries, such as JQuery, are using the > incorrect encoding for URLs sent to OLingo based OData v2 services. > According to the OData V2 standard, the separator for encoded URLs is %20. > However, in many cases when developers talk about "URL encoding", they use > Java functions like "URLEncoder.encode()" to encode the parameters for their > HTTP request. JQuery seems to utilise a similar function in JavaScript. > Now these functions are based on the HTTP forms encoding standard, so they > use "+" as a separator. > If would be small but grateful addition to the OLingo URI parser to accept > both separator characters. Maybe with a config option to follow the standard > (so only accept %20) or to be more relaxed (and accept both). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OLINGO-1147) Entity read is not working due to normalization in JPAQueryBuilder
[
https://issues.apache.org/jira/browse/OLINGO-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16083440#comment-16083440
]
Michael Bolz commented on OLINGO-1147:
--
I currently do not have the time for a deep lock into the issue.
However after a quick look into the code a solution could be to remove such
property value parts like the {{‘ENTITY_NAME.1.2’}} before the normalisation
needed check.
Then we do the check on the query with removed parameter and if it is still
true proceed the normalisation with the full query.
Regards, Michael
> Entity read is not working due to normalization in JPAQueryBuilder
> --
>
> Key: OLINGO-1147
> URL: https://issues.apache.org/jira/browse/OLINGO-1147
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Daniel Horvath
>Priority: Blocker
>
> Hello Colleagues,
> We have found a bug in JPAQueryBuilder. In version 2.0.7 it is working fine
> but in version 2.0.8 where the normalizeMembers() method is added it fails on
> certain queries.
> The error happens in line 180: {color:red}return
> em.createQuery(normalizeMembers(jpqlStatement.toString()));{color}
> The query before normalisation:
> *SELECT E1 FROM Entity E1 WHERE E1.id = 'ENTITY_NAME.1.2'*
> After the normalisation the query looks like this (an invalid query):
> *SELECT DISTINCT E1 FROM Entity E1 JOIN 'ENTITY_NAME.1 R1 WHERE E1.id = R1.2'*
> The regular expression finds this query as it should be normalised because of
> the id part ('ENTITY_NAME.1.2'). As we found out, this is caused by the point
> characters in the id field. It should not be found by the reg. exp. because
> this is inside of apostrophes.
> If you have further questions, please contact me.
> Best regards,
> Daniel
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OLINGO-1141) Release Olingo 2 Version 2.0.9
[ https://issues.apache.org/jira/browse/OLINGO-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz closed OLINGO-1141. > Release Olingo 2 Version 2.0.9 > -- > > Key: OLINGO-1141 > URL: https://issues.apache.org/jira/browse/OLINGO-1141 > Project: Olingo > Issue Type: Task > Components: odata2-annotation, odata2-core, odata2-jpa >Affects Versions: V2 2.0.8 >Reporter: Michael Bolz >Assignee: Michael Bolz >Priority: Minor > Fix For: V2 2.0.9 > > > Prepare for and create release of Olingo 2 Version 2.0.9 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OLINGO-1141) Release Olingo 2 Version 2.0.9
[ https://issues.apache.org/jira/browse/OLINGO-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz resolved OLINGO-1141. -- Resolution: Fixed Done with [this commit|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=220b289c54b17ce449ad1bc80f45f8c41a930083] (and [tag 2.0.9)|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=shortlog;h=refs/tags/2.0.9]. > Release Olingo 2 Version 2.0.9 > -- > > Key: OLINGO-1141 > URL: https://issues.apache.org/jira/browse/OLINGO-1141 > Project: Olingo > Issue Type: Task > Components: odata2-annotation, odata2-core, odata2-jpa >Affects Versions: V2 2.0.8 >Reporter: Michael Bolz >Assignee: Michael Bolz >Priority: Minor > Fix For: V2 2.0.9 > > > Prepare for and create release of Olingo 2 Version 2.0.9 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OLINGO-1141) Release Olingo 2 Version 2.0.9
[ https://issues.apache.org/jira/browse/OLINGO-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz reassigned OLINGO-1141: Assignee: Michael Bolz > Release Olingo 2 Version 2.0.9 > -- > > Key: OLINGO-1141 > URL: https://issues.apache.org/jira/browse/OLINGO-1141 > Project: Olingo > Issue Type: Task > Components: odata2-annotation, odata2-core, odata2-jpa >Affects Versions: V2 2.0.8 >Reporter: Michael Bolz >Assignee: Michael Bolz >Priority: Minor > Fix For: V2 2.0.9 > > > Prepare for and create release of Olingo 2 Version 2.0.9 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OLINGO-1141) Release Olingo 2 Version 2.0.9
Michael Bolz created OLINGO-1141: Summary: Release Olingo 2 Version 2.0.9 Key: OLINGO-1141 URL: https://issues.apache.org/jira/browse/OLINGO-1141 Project: Olingo Issue Type: Task Components: odata2-annotation, odata2-core, odata2-jpa Affects Versions: V2 2.0.8 Reporter: Michael Bolz Priority: Minor Fix For: V2 2.0.9 Prepare for and create release of Olingo 2 Version 2.0.9 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OLINGO-1140) Support of OSGi bundle wrapping
[
https://issues.apache.org/jira/browse/OLINGO-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-1140:
-
Affects Version/s: (was: (Java) V4 4.3.0)
V2 2.0.8
> Support of OSGi bundle wrapping
> ---
>
> Key: OLINGO-1140
> URL: https://issues.apache.org/jira/browse/OLINGO-1140
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Johannes Hoenger
>
> *Context*
> We as OSGi developers face a challenge when using third-party libraries like
> Olingo that OSGi bundles may not be provided.
> Since Olingo does also not provide a bundle we opted for the most common
> solution. We wrapped the Olingo library using [Apache
> Felix|http://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html].
> For more details about wrapping please refer to this link [Wrapping Libraries
> to OSGi Bundles|http://bnd.bndtools.org/chapters/390-wrapping.html] and
> [Creating wrapper OSGi
> bundles|https://cwiki.apache.org/confluence/display/SMX4/1.+Beginner+-+Creating+wrapper+OSGi+bundles].
> *Request*
> An inherent property of the wrapping is that the namespace of the wrapped
> artifact changes. This is usually not an issue.
> However, when in the code is a package name hardcoded which leads to issue in
> our software component.
> The issue occurs at line 63 in the class RuntimeDelegate. Please refer to the
> following link
> https://github.com/apache/olingo-odata2/blob/b33cdc411ac8731162266ebb19ae97a90ca88be9/odata2-lib/odata-api/src/main/java/org/apache/olingo/odata2/api/rt/RuntimeDelegate.java#L51-L76
> The aforementioned lined throws in our OSGi components the following exception
> {code:title=exception.log|borderStyle=solid}
> Exception:
> org.apache.olingo.odata2.api.rt.RuntimeDelegate$RuntimeDelegateException:
> java.lang.ClassNotFoundException:
> org.apache.olingo.odata2.core.rt.RuntimeDelegateImpl cannot be found by
>
> org.apache.olingo.odata2.api.rt.RuntimeDelegate$RuntimeDelegateException:
> java.lang.ClassNotFoundException:
> org.apache.olingo.odata2.core.rt.RuntimeDelegateImpl cannot be found by
>
> at
> org.apache.olingo.odata2.api.rt.RuntimeDelegate.getInstance(RuntimeDelegate.java:73)
> at
> org.apache.olingo.odata2.api.rt.RuntimeDelegate.extractExceptionMessage(RuntimeDelegate.java:236)
> at
> org.apache.olingo.odata2.api.exception.ODataMessageException.getMessage(ODataMessageException.java:127)
> at java.lang.Throwable.getLocalizedMessage(Throwable.java:391)
> at java.lang.Throwable.toString(Throwable.java:480)
> at java.lang.Throwable.(Throwable.java:311)
> at java.lang.Exception.(Exception.java:102)
> at
> org.apache.olingo.odata2.api.exception.ODataException.(ODataException.java:42)
> at
> org.apache.olingo.odata2.api.exception.ODataMessageException.(ODataMessageException.java:75)
> at
> org.apache.olingo.odata2.api.exception.ODataMessageException.(ODataMessageException.java:63)
> at
> org.apache.olingo.odata2.api.edm.EdmException.(EdmException.java:48)
> at
> org.apache.olingo.odata2.api.edm.EdmLiteralException.(EdmLiteralException.java:43)
> at
> org.apache.olingo.odata2.core.edm.EdmSimpleTypeFacadeImpl.parseUriLiteral(EdmSimpleTypeFacadeImpl.java:76)
> at
> org.apache.olingo.odata2.core.uri.expression.Tokenizer.checkForLiteral(Tokenizer.java:171)
> at
> org.apache.olingo.odata2.core.uri.expression.Tokenizer.tokenize(Tokenizer.java:153)
> at
> org.apache.olingo.odata2.core.uri.expression.FilterParserImpl.parseFilterString(FilterParserImpl.java:89)
> at
> org.apache.olingo.odata2.core.uri.expression.FilterParserImpl.parseFilterString(FilterParserImpl.java:80)
> {code}
> This line is, as far as we can tell, the only line which is incompatible with
> the OSGi wrapping approach. Is is possible to provide a solution for this
> case?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OLINGO-1139) Merge of GitHub pull request (about typos)
[ https://issues.apache.org/jira/browse/OLINGO-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz resolved OLINGO-1139. -- Resolution: Fixed > Merge of GitHub pull request (about typos) > -- > > Key: OLINGO-1139 > URL: https://issues.apache.org/jira/browse/OLINGO-1139 > Project: Olingo > Issue Type: Improvement > Components: odata2-jpa >Affects Versions: V2 2.0.8 >Reporter: Michael Bolz >Assignee: Michael Bolz >Priority: Minor > Fix For: V2 2.0.9 > > > Merge of GitHub pull request (about typos): > https://github.com/apache/olingo-odata2/pull/12/files -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OLINGO-1139) Merge of GitHub pull request (about typos)
[ https://issues.apache.org/jira/browse/OLINGO-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz closed OLINGO-1139. > Merge of GitHub pull request (about typos) > -- > > Key: OLINGO-1139 > URL: https://issues.apache.org/jira/browse/OLINGO-1139 > Project: Olingo > Issue Type: Improvement > Components: odata2-jpa >Affects Versions: V2 2.0.8 >Reporter: Michael Bolz >Assignee: Michael Bolz >Priority: Minor > Fix For: V2 2.0.9 > > > Merge of GitHub pull request (about typos): > https://github.com/apache/olingo-odata2/pull/12/files -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OLINGO-1119) UriInfoType enum change to private breaking change
[ https://issues.apache.org/jira/browse/OLINGO-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1119: - Issue Type: Question (was: Bug) > UriInfoType enum change to private breaking change > -- > > Key: OLINGO-1119 > URL: https://issues.apache.org/jira/browse/OLINGO-1119 > Project: Olingo > Issue Type: Question > Components: odata2-jpa >Affects Versions: V2 2.0.8 >Reporter: Benjamin Runnels >Assignee: Michael Bolz > > This changeset switched JPAQueryBuilder.UriInfoType to private. > https://github.com/apache/olingo-odata2/commit/3ed58899d76c57ef8a26a3a02098c736f4740856 > I have code extending ODataJPAQueryExtensionEntityListener that was using the > UriInfoType enum. I upgraded from olingo 2.0.7 to olingo 2.0.8 and making > that enum private is a breaking change. Is there a reason this was changed? > Do you have an alternative I should be using? > Here's a link to the CustomQueryBuilder that it breaks. > https://github.com/hwestphal/spring-boot-odata/blob/master/src/main/java/io/github/hwestphal/odata/server/CustomJpaQueryBuilder.java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OLINGO-1119) UriInfoType enum change to private breaking change
[
https://issues.apache.org/jira/browse/OLINGO-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049987#comment-16049987
]
Michael Bolz commented on OLINGO-1119:
--
Hello [~kra...@kraven.org],
In general code from the library core should not be directly used because for
those parts it can not be guaranteed that all changes as backward compatible.
The reason for the code change was that the {{UriInfoType}} enum is only used
by the {{JPAQueryBuilder}} and should therefore not exposed.
In the {{CustomJpaQueryBuilder}} you mentioned the use of the Olingo internal
(core) {{UriInfoType}} is really not required or necessary.
It should be replaced by an own (e.g. in the {{CustomJpaQueryBuilder}} defined)
enum.
Kind Regards, Michael
> UriInfoType enum change to private breaking change
> --
>
> Key: OLINGO-1119
> URL: https://issues.apache.org/jira/browse/OLINGO-1119
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
>Affects Versions: V2 2.0.8
>Reporter: Benjamin Runnels
>Assignee: Michael Bolz
>
> This changeset switched JPAQueryBuilder.UriInfoType to private.
> https://github.com/apache/olingo-odata2/commit/3ed58899d76c57ef8a26a3a02098c736f4740856
> I have code extending ODataJPAQueryExtensionEntityListener that was using the
> UriInfoType enum. I upgraded from olingo 2.0.7 to olingo 2.0.8 and making
> that enum private is a breaking change. Is there a reason this was changed?
> Do you have an alternative I should be using?
> Here's a link to the CustomQueryBuilder that it breaks.
> https://github.com/hwestphal/spring-boot-odata/blob/master/src/main/java/io/github/hwestphal/odata/server/CustomJpaQueryBuilder.java
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OLINGO-1119) UriInfoType enum change to private breaking change
[ https://issues.apache.org/jira/browse/OLINGO-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz resolved OLINGO-1119. -- Resolution: Information Provided > UriInfoType enum change to private breaking change > -- > > Key: OLINGO-1119 > URL: https://issues.apache.org/jira/browse/OLINGO-1119 > Project: Olingo > Issue Type: Question > Components: odata2-jpa >Affects Versions: V2 2.0.8 >Reporter: Benjamin Runnels >Assignee: Michael Bolz >Priority: Minor > > This changeset switched JPAQueryBuilder.UriInfoType to private. > https://github.com/apache/olingo-odata2/commit/3ed58899d76c57ef8a26a3a02098c736f4740856 > I have code extending ODataJPAQueryExtensionEntityListener that was using the > UriInfoType enum. I upgraded from olingo 2.0.7 to olingo 2.0.8 and making > that enum private is a breaking change. Is there a reason this was changed? > Do you have an alternative I should be using? > Here's a link to the CustomQueryBuilder that it breaks. > https://github.com/hwestphal/spring-boot-odata/blob/master/src/main/java/io/github/hwestphal/odata/server/CustomJpaQueryBuilder.java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OLINGO-1119) UriInfoType enum change to private breaking change
[ https://issues.apache.org/jira/browse/OLINGO-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated OLINGO-1119: - Priority: Minor (was: Major) > UriInfoType enum change to private breaking change > -- > > Key: OLINGO-1119 > URL: https://issues.apache.org/jira/browse/OLINGO-1119 > Project: Olingo > Issue Type: Question > Components: odata2-jpa >Affects Versions: V2 2.0.8 >Reporter: Benjamin Runnels >Assignee: Michael Bolz >Priority: Minor > > This changeset switched JPAQueryBuilder.UriInfoType to private. > https://github.com/apache/olingo-odata2/commit/3ed58899d76c57ef8a26a3a02098c736f4740856 > I have code extending ODataJPAQueryExtensionEntityListener that was using the > UriInfoType enum. I upgraded from olingo 2.0.7 to olingo 2.0.8 and making > that enum private is a breaking change. Is there a reason this was changed? > Do you have an alternative I should be using? > Here's a link to the CustomQueryBuilder that it breaks. > https://github.com/hwestphal/spring-boot-odata/blob/master/src/main/java/io/github/hwestphal/odata/server/CustomJpaQueryBuilder.java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OLINGO-1119) UriInfoType enum change to private breaking change
[ https://issues.apache.org/jira/browse/OLINGO-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz reassigned OLINGO-1119: Assignee: Michael Bolz > UriInfoType enum change to private breaking change > -- > > Key: OLINGO-1119 > URL: https://issues.apache.org/jira/browse/OLINGO-1119 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.8 >Reporter: Benjamin Runnels >Assignee: Michael Bolz > > This changeset switched JPAQueryBuilder.UriInfoType to private. > https://github.com/apache/olingo-odata2/commit/3ed58899d76c57ef8a26a3a02098c736f4740856 > I have code extending ODataJPAQueryExtensionEntityListener that was using the > UriInfoType enum. I upgraded from olingo 2.0.7 to olingo 2.0.8 and making > that enum private is a breaking change. Is there a reason this was changed? > Do you have an alternative I should be using? > Here's a link to the CustomQueryBuilder that it breaks. > https://github.com/hwestphal/spring-boot-odata/blob/master/src/main/java/io/github/hwestphal/odata/server/CustomJpaQueryBuilder.java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OLINGO-1107) UriDecoder should use java.net.URLDecoder
[
https://issues.apache.org/jira/browse/OLINGO-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968058#comment-15968058
]
Michael Bolz commented on OLINGO-1107:
--
Hi,
as long the relaxation only affects the client it is fine for me.
As far as I understand the change, afterwards the client can handle {{+}} as
empty space
and for the server the behaviour will not be changed, right?
Best Regards, Michael
> UriDecoder should use java.net.URLDecoder
> -
>
> Key: OLINGO-1107
> URL: https://issues.apache.org/jira/browse/OLINGO-1107
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
>Affects Versions: (Java) V4 4.3.0
>Reporter: Jon McEwen
>
> Query filters are incorrectly parsed, because the
> org.apache.olingo.commons.core.Decoder doesn't convert '+' to space.
> Simple fix is to use java.net.URLDecoder instead (line 85):
> {{return URLDecoder.decode(encoded, "UTF-8");}}
> Additional unit test:
> {code:Java}
> @Test
> public void decodePlusAsSpace() throws Exception{
> checkOption("%24filter=PaymentStatus+eq+%27Cleared%27", "$filter",
> "PaymentStatus eq 'Cleared'");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (OLINGO-1064) ComplexType is deserialized as Primitive Type if the value is NULL
[
https://issues.apache.org/jira/browse/OLINGO-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated OLINGO-1064:
-
Component/s: (was: odata2-core)
> ComplexType is deserialized as Primitive Type if the value is NULL
> --
>
> Key: OLINGO-1064
> URL: https://issues.apache.org/jira/browse/OLINGO-1064
> Project: Olingo
> Issue Type: Bug
> Components: odata4-client, odata4-commons
>Affects Versions: (Java) V4 4.2.0
>Reporter: Punith DG
>Assignee: Christian Amend
> Attachments: complexType.png
>
>
> The ODataClient deserializer wrongly converts the Complex Type field to
> Primitive Type field if the value received for the complex type is NULL.
> e.g. on querying Person data from OData TripPin service
> (https://services.odata.org/TripPinRESTierService) I received below JSON
> response.
> {
> "@odata.context":
> "http://services.odata.org/TripPinRESTierService/(S(myhztseklikbg41mbg03ugk5))/$metadata#People(AddressInfo,FavoriteFeature,FirstName,HomeAddress,LastName,UserName)",
> "value": [{
> "FavoriteFeature": "Feature1",
> "FirstName": "Angel",
> "Gender": "Female",
> "LastName": "Huffman",
> "UserName": "angelhuffman",
> "AddressInfo": [{
> "Address": "55 Grizzly Peak Rd.",
> "City": {
> "Name": "Butte",
> "CountryRegion": "United States",
> "Region": "MT"
> }
> }],
> "HomeAddress": null
> }]
> }
> See that 'HomeAddress' is ComplexType of type 'Location' and received 'null'
> value.
> Similarly, ComplexType property 'City' is deserialized as Primitive Type in
> the below response.
> "HomeAddress": {
> "Address": null,
> "City": null
> }
> When you deserialize and get an entity, the HomeAddress property of the
> Person entity is set to Primitive Type with null value. This could be complex
> type?
> Metadata URL - http://tinyurl.com/gm8vomc
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (OLINGO-1095) JPAQueryBuilder.normalizeMembers encounters issue when EmbedId
[ https://issues.apache.org/jira/browse/OLINGO-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961248#comment-15961248 ] Michael Bolz commented on OLINGO-1095: -- Okay, then I close this issue and it will be part of the next release. Thanks again for your contribution and help by this issue. Wish you a nice time, Regards, Michael > JPAQueryBuilder.normalizeMembers encounters issue when EmbedId > -- > > Key: OLINGO-1095 > URL: https://issues.apache.org/jira/browse/OLINGO-1095 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.8 >Reporter: evildracula >Assignee: Michael Bolz > Fix For: V2 2.0.9 > > Attachments: TypeCastSc1.png, TypeCastSc2.png > > > org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilder > normalizeMembers failed to process EmbedKeyId when JPA query is: > SELECT E1 FROM EndUser E1 WHERE E1.id.pid= 'T001' AND E1.id.rid= 'E001' > the normalized query will be: > SELECT DISTINCT E1 FROM EndUser E1 JOIN E1.id R1 WHERE R1.pid = 'T001' AND > R1.rid = 'E001' > |This will cause problem when validated by boolean > org.eclipse.persistence.jpa.jpql.AbstractSemanticValidator.validateCollectionValuedPathExpression(Expression > expression, boolean collectionTypeOnly)| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OLINGO-1095) JPAQueryBuilder.normalizeMembers encounters issue when EmbedId
[ https://issues.apache.org/jira/browse/OLINGO-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957226#comment-15957226 ] Michael Bolz commented on OLINGO-1095: -- Hi [~evildracula], I'am really sorry but neither I can re-produce your issue nor can I understand the problem of the Eclipse? compiler. Do you know what Java compiler is used by your Eclipse? Best regards, Michael > JPAQueryBuilder.normalizeMembers encounters issue when EmbedId > -- > > Key: OLINGO-1095 > URL: https://issues.apache.org/jira/browse/OLINGO-1095 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.8 >Reporter: evildracula >Assignee: Michael Bolz > Fix For: V2 2.0.9 > > Attachments: TypeCastSc1.png, TypeCastSc2.png > > > org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilder > normalizeMembers failed to process EmbedKeyId when JPA query is: > SELECT E1 FROM EndUser E1 WHERE E1.id.pid= 'T001' AND E1.id.rid= 'E001' > the normalized query will be: > SELECT DISTINCT E1 FROM EndUser E1 JOIN E1.id R1 WHERE R1.pid = 'T001' AND > R1.rid = 'E001' > |This will cause problem when validated by boolean > org.eclipse.persistence.jpa.jpql.AbstractSemanticValidator.validateCollectionValuedPathExpression(Expression > expression, boolean collectionTypeOnly)| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OLINGO-1095) JPAQueryBuilder.normalizeMembers encounters issue when EmbedId
[ https://issues.apache.org/jira/browse/OLINGO-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15951465#comment-15951465 ] Michael Bolz commented on OLINGO-1095: -- What happens when you build the project with maven on the command line? Do you have the Oracle JDK or some other? I tested again with JDK 6/7/8 without any issue and the [Apache Jenkins|https://builds.apache.org/view/Olingo/job/olingo-odata2/1332/] also have no compiler issue. > JPAQueryBuilder.normalizeMembers encounters issue when EmbedId > -- > > Key: OLINGO-1095 > URL: https://issues.apache.org/jira/browse/OLINGO-1095 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.8 >Reporter: evildracula >Assignee: Michael Bolz > Fix For: V2 2.0.9 > > > org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilder > normalizeMembers failed to process EmbedKeyId when JPA query is: > SELECT E1 FROM EndUser E1 WHERE E1.id.pid= 'T001' AND E1.id.rid= 'E001' > the normalized query will be: > SELECT DISTINCT E1 FROM EndUser E1 JOIN E1.id R1 WHERE R1.pid = 'T001' AND > R1.rid = 'E001' > |This will cause problem when validated by boolean > org.eclipse.persistence.jpa.jpql.AbstractSemanticValidator.validateCollectionValuedPathExpression(Expression > expression, boolean collectionTypeOnly)| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OLINGO-1095) JPAQueryBuilder.normalizeMembers encounters issue when EmbedId
[ https://issues.apache.org/jira/browse/OLINGO-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949537#comment-15949537 ] Michael Bolz commented on OLINGO-1095: -- Hi [~evildracula], what version do you use and what for difficulties do you have? I compiled/runned it with Java 6 and 8 without a problem. Regards, Michael > JPAQueryBuilder.normalizeMembers encounters issue when EmbedId > -- > > Key: OLINGO-1095 > URL: https://issues.apache.org/jira/browse/OLINGO-1095 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.8 >Reporter: evildracula >Assignee: Michael Bolz > Fix For: V2 2.0.9 > > > org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilder > normalizeMembers failed to process EmbedKeyId when JPA query is: > SELECT E1 FROM EndUser E1 WHERE E1.id.pid= 'T001' AND E1.id.rid= 'E001' > the normalized query will be: > SELECT DISTINCT E1 FROM EndUser E1 JOIN E1.id R1 WHERE R1.pid = 'T001' AND > R1.rid = 'E001' > |This will cause problem when validated by boolean > org.eclipse.persistence.jpa.jpql.AbstractSemanticValidator.validateCollectionValuedPathExpression(Expression > expression, boolean collectionTypeOnly)| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (OLINGO-1097) Failure while parsing HTTP header fields joined by multiple whitespaces
[
https://issues.apache.org/jira/browse/OLINGO-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz resolved OLINGO-1097.
--
Resolution: Fixed
> Failure while parsing HTTP header fields joined by multiple whitespaces
> ---
>
> Key: OLINGO-1097
> URL: https://issues.apache.org/jira/browse/OLINGO-1097
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Dmitry Tretyakov
>Assignee: Michael Bolz
> Labels: patch
> Fix For: V2 2.0.9
>
> Attachments:
> 0002-OLINGO-1097-Failure-while-parsing-HTTP-header-fields.patch
>
>
> `RestUtil` while parsing HTTP header values allow to join multiple field
> values with comma and only one white space it causes that after parsing
> values are prefixed by white spaces which causes exceptions in `ContentType`
> instantiation and as result leads to BadRequestException.
> See RFC 2616 4.2:
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
> Example of failing HTTP accept header field value:
> {code}
> application/atom+xml, application/xml
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (OLINGO-1097) Failure while parsing HTTP header fields joined by multiple whitespaces
[
https://issues.apache.org/jira/browse/OLINGO-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz closed OLINGO-1097.
> Failure while parsing HTTP header fields joined by multiple whitespaces
> ---
>
> Key: OLINGO-1097
> URL: https://issues.apache.org/jira/browse/OLINGO-1097
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Dmitry Tretyakov
>Assignee: Michael Bolz
> Labels: patch
> Fix For: V2 2.0.9
>
> Attachments:
> 0002-OLINGO-1097-Failure-while-parsing-HTTP-header-fields.patch
>
>
> `RestUtil` while parsing HTTP header values allow to join multiple field
> values with comma and only one white space it causes that after parsing
> values are prefixed by white spaces which causes exceptions in `ContentType`
> instantiation and as result leads to BadRequestException.
> See RFC 2616 4.2:
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
> Example of failing HTTP accept header field value:
> {code}
> application/atom+xml, application/xml
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
