[jira] [Commented] (OLINGO-1295) jackson upgrade odata-server and odata-client
[ https://issues.apache.org/jira/browse/OLINGO-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626490#comment-16626490 ] Michael commented on OLINGO-1295: - Here's the security vulnerability report against jackson-dataformat-xml ... [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7051] There's one for jackson-core but I am aware of that one only through private channels. I'll let you know if I can provide more information it later. > jackson upgrade odata-server and odata-client > - > > Key: OLINGO-1295 > URL: https://issues.apache.org/jira/browse/OLINGO-1295 > Project: Olingo > Issue Type: Improvement > Components: odata2-core, odata4-client >Affects Versions: (Java) V4 4.5.0 >Reporter: Michael >Priority: Minor > > Upgrade Upgrade jackson core, databind, annotations, dataformat-xml, > jaxrs-json-provider. > [https://github.com/apache/olingo-odata4/blob/003f0f4ffa07cbbc7500c1bece37a41813eb670e/pom.xml#L86] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OLINGO-1295) jackson upgrade odata-server and odata-client
[ https://issues.apache.org/jira/browse/OLINGO-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626484#comment-16626484 ] Michael edited comment on OLINGO-1295 at 9/24/18 9:31 PM: -- Here's a PR for the pom change that reproduces the infinite loop in MetadataValidationTest.checkInValidV4XMLMetadataWithNoSchemas() [https://github.com/apache/oli|https://github.com/apache/olingo-odata4/pull/33] [ngo-odata4/pull/33|https://github.com/apache/olingo-odata4/pull/33] I haven't yet worked out a fix. I can open a bug but what version should I open it against given that the jackson upgrade commit that reproduces the problem only exists on my personal fork(https://github.com/msgroi/olingo-odata4/commits/master)? was (Author: michaelsgroi): Here's a PR for the pom change that reproduces the infinite loop in MetadataValidationTest.checkInValidV4XMLMetadataWithNoSchemas() [https://github.com/apache/olingo-odata4/pull/33] I haven't yet worked out a fix. > jackson upgrade odata-server and odata-client > - > > Key: OLINGO-1295 > URL: https://issues.apache.org/jira/browse/OLINGO-1295 > Project: Olingo > Issue Type: Improvement > Components: odata2-core, odata4-client >Affects Versions: (Java) V4 4.5.0 >Reporter: Michael >Priority: Minor > > Upgrade Upgrade jackson core, databind, annotations, dataformat-xml, > jaxrs-json-provider. > [https://github.com/apache/olingo-odata4/blob/003f0f4ffa07cbbc7500c1bece37a41813eb670e/pom.xml#L86] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1295) jackson upgrade odata-server and odata-client
[ https://issues.apache.org/jira/browse/OLINGO-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626484#comment-16626484 ] Michael commented on OLINGO-1295: - Here's a PR for the pom change that reproduces the infinite loop in MetadataValidationTest.checkInValidV4XMLMetadataWithNoSchemas() [https://github.com/apache/olingo-odata4/pull/33] I haven't yet worked out a fix. > jackson upgrade odata-server and odata-client > - > > Key: OLINGO-1295 > URL: https://issues.apache.org/jira/browse/OLINGO-1295 > Project: Olingo > Issue Type: Improvement > Components: odata2-core, odata4-client >Affects Versions: (Java) V4 4.5.0 >Reporter: Michael >Priority: Minor > > Upgrade Upgrade jackson core, databind, annotations, dataformat-xml, > jaxrs-json-provider. > [https://github.com/apache/olingo-odata4/blob/003f0f4ffa07cbbc7500c1bece37a41813eb670e/pom.xml#L86] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1295) jackson upgrade odata-server and odata-client
[ https://issues.apache.org/jira/browse/OLINGO-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626290#comment-16626290 ] Ramesh Reddy commented on OLINGO-1295: -- Can you debug and submit a patch why there is a infinite loop in the test? > jackson upgrade odata-server and odata-client > - > > Key: OLINGO-1295 > URL: https://issues.apache.org/jira/browse/OLINGO-1295 > Project: Olingo > Issue Type: Improvement > Components: odata2-core, odata4-client >Affects Versions: (Java) V4 4.5.0 >Reporter: Michael >Priority: Minor > > Upgrade Upgrade jackson core, databind, annotations, dataformat-xml, > jaxrs-json-provider. > [https://github.com/apache/olingo-odata4/blob/003f0f4ffa07cbbc7500c1bece37a41813eb670e/pom.xml#L86] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1295) jackson upgrade odata-server and odata-client
[ https://issues.apache.org/jira/browse/OLINGO-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626207#comment-16626207 ] Michael commented on OLINGO-1295: - I have upgraded jackson to 2.9.6 on a fork ... [https://github.com/msgroi/olingo-odata4/commit/d82aac9ee9b86ae3d2186352696d5eeb1b19f9c6] I had to ignore MetadataValidationTest.checkInValidV4XMLMetadataWithNoSchemas(). It runs in an infinite loop. Stack trace shows where it's looping ... "main" #1 prio=5 os_prio=31 tid=0x7f818c00 nid=0x1803 runnable [0x71edf000] java.lang.Thread.State: RUNNABLE at org.apache.olingo.client.core.edm.xml.ClientCsdlEdmx$EdmxDeserializer.doDeserialize(ClientCsdlEdmx.java:79) at org.apache.olingo.client.core.edm.xml.ClientCsdlEdmx$EdmxDeserializer.doDeserialize(ClientCsdlEdmx.java:71) at org.apache.olingo.client.core.edm.xml.AbstractClientCsdlEdmDeserializer.deserialize(AbstractClientCsdlEdmDeserializer.java:60) at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4001) at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3058) at org.apache.olingo.client.core.serialization.ClientODataDeserializerImpl.toMetadata(ClientODataDeserializerImpl.java:139) at org.apache.olingo.client.core.MetadataValidationTest.checkInValidV4XMLMetadataWithNoSchemas(MetadataValidationTest.java:744) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.junit.runner.JUnitCore.run(JUnitCore.java:160) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70 Note that backtracking versions of jackson reveals that the hanging started when upgrading from jackson 2.8.9 to 2.90. Aside from that, all tests pass. Any reason that we should be concerned that jackson 2.9.6 won't work with both odata-client and odata-server? > jackson upgrade odata-server and odata-client > - > > Key: OLINGO-1295 > URL: https://issues.apache.org/jira/browse/OLINGO-1295 > Project: Olingo > Issue Type: Improvement > Components: odata2-core, odata4-client >Affects Versions: (Java) V4 4.5.0 >Reporter: Michael >Priority: Minor > > Upgrade Upgrade jackson core, databind, annotations, dataformat-xml, > jaxrs-json-provider. > [https://github.com/apache/olingo-odata4/blob/003f0f4ffa07cbbc7500c1bece37a41813eb670e/pom.xml#L86] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OLINGO-1295) jackson upgrade odata-server and odata-client
Michael created OLINGO-1295: --- Summary: jackson upgrade odata-server and odata-client Key: OLINGO-1295 URL: https://issues.apache.org/jira/browse/OLINGO-1295 Project: Olingo Issue Type: Improvement Components: odata2-core, odata4-client Affects Versions: (Java) V4 4.5.0 Reporter: Michael Upgrade Upgrade jackson core, databind, annotations, dataformat-xml, jaxrs-json-provider. [https://github.com/apache/olingo-odata4/blob/003f0f4ffa07cbbc7500c1bece37a41813eb670e/pom.xml#L86] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1293) Srid is not exposed by the MetadataDocument Serializers
[ https://issues.apache.org/jira/browse/OLINGO-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1293. -- Resolution: Fixed Applied changes with https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=4b77243d9e518a9a0e5aae3f4346d42acccb20b4 > Srid is not exposed by the MetadataDocument Serializers > --- > > Key: OLINGO-1293 > URL: https://issues.apache.org/jira/browse/OLINGO-1293 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Assignee: Ramesh Reddy >Priority: Major > Fix For: 4.6.0 > > > Property level srid values are not exposed in the metadata. Given > OLINGO-1292 this makes it impossible to determine the srid when using json > results. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1292) Json Serialization of geometry value does not allow for an SRID
[ https://issues.apache.org/jira/browse/OLINGO-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1292. -- Resolution: Fixed Applied the changes with merge https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=b09dde0b3991f458dec1e90e74e6fce0639cb849 > Json Serialization of geometry value does not allow for an SRID > --- > > Key: OLINGO-1292 > URL: https://issues.apache.org/jira/browse/OLINGO-1292 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Assignee: Ramesh Reddy >Priority: Major > Fix For: 4.6.0 > > > Due to > [https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/server-core/src/main/java/org/apache/olingo/server/core/serializer/json/ODataJsonSerializer.java#L991] > an srid cannot be associated with a value - even if it's the default 0 or > 4326 for geometry or geography respectively. > Looking at the reference service output > [https://services.odata.org/TripPinRESTierService/Airports] > the srid is associated, and it's already part of the client serialization > logic > [https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/client-core/src/main/java/org/apache/olingo/client/core/serialization/JsonGeoValueSerializer.java#L42] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-1294) Polygon should support multiple interior holes
[ https://issues.apache.org/jira/browse/OLINGO-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1294. -- Resolution: Fixed Applied the changes to master after review and test checking. https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=ebdf0d3e3a604133e1a54e79aecd7299e6b7c55e > Polygon should support multiple interior holes > -- > > Key: OLINGO-1294 > URL: https://issues.apache.org/jira/browse/OLINGO-1294 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Assignee: Ramesh Reddy >Priority: Major > Fix For: 4.6.0 > > > The Polygon value object is limited to a single interior. It should hold any > number of holes, which is allowed by the grammar > https://docs.oasis-open.org/odata/odata/v4.0/os/abnf/odata-abnf-construction-rules.txt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1293) Srid is not exposed by the MetadataDocument Serializers
[ https://issues.apache.org/jira/browse/OLINGO-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1293: - Fix Version/s: 4.6.0 > Srid is not exposed by the MetadataDocument Serializers > --- > > Key: OLINGO-1293 > URL: https://issues.apache.org/jira/browse/OLINGO-1293 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Assignee: Ramesh Reddy >Priority: Major > Fix For: 4.6.0 > > > Property level srid values are not exposed in the metadata. Given > OLINGO-1292 this makes it impossible to determine the srid when using json > results. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1294) Polygon should support multiple interior holes
[ https://issues.apache.org/jira/browse/OLINGO-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1294: - Fix Version/s: 4.6.0 > Polygon should support multiple interior holes > -- > > Key: OLINGO-1294 > URL: https://issues.apache.org/jira/browse/OLINGO-1294 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Assignee: Ramesh Reddy >Priority: Major > Fix For: 4.6.0 > > > The Polygon value object is limited to a single interior. It should hold any > number of holes, which is allowed by the grammar > https://docs.oasis-open.org/odata/odata/v4.0/os/abnf/odata-abnf-construction-rules.txt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1292) Json Serialization of geometry value does not allow for an SRID
[ https://issues.apache.org/jira/browse/OLINGO-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1292: - Fix Version/s: 4.6.0 > Json Serialization of geometry value does not allow for an SRID > --- > > Key: OLINGO-1292 > URL: https://issues.apache.org/jira/browse/OLINGO-1292 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Assignee: Ramesh Reddy >Priority: Major > Fix For: 4.6.0 > > > Due to > [https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/server-core/src/main/java/org/apache/olingo/server/core/serializer/json/ODataJsonSerializer.java#L991] > an srid cannot be associated with a value - even if it's the default 0 or > 4326 for geometry or geography respectively. > Looking at the reference service output > [https://services.odata.org/TripPinRESTierService/Airports] > the srid is associated, and it's already part of the client serialization > logic > [https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/client-core/src/main/java/org/apache/olingo/client/core/serialization/JsonGeoValueSerializer.java#L42] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OLINGO-570) Implement OData Json Metadocument Serializer/Parser
[ https://issues.apache.org/jira/browse/OLINGO-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-570. - Resolution: Duplicate > Implement OData Json Metadocument Serializer/Parser > --- > > Key: OLINGO-570 > URL: https://issues.apache.org/jira/browse/OLINGO-570 > Project: Olingo > Issue Type: Improvement > Components: odata4-client, odata4-server >Affects Versions: (Java) V4 4.0.0-beta-02 >Reporter: Christian Amend >Assignee: Ramesh Reddy >Priority: Major > Labels: gsoc2015, java, mentor, xml > Attachments: jsonMeta1.diff, jsonMeta2.diff, jsonMeta3.diff, > jsonMeta4.diff, jsonMetaDeserializer1.diff, jsonMetaDeserializer2.diff, > jsonMetaDeserializer3.diff, jsonMetaDeserializer4.diff > > > The Olingo project is currently working on implementing the V4 OData > specification published by oasis. The current version of the specification > only specifies a metadata document in xml format. This can be problematic on > android devices where no native xml parser is available. In a newer version > of this specification a new metadata format will be specified in Json. > The goal of this issue would be to implement a serializer which can create a > payload based on the new specification. Afterwards the Olingo client library > must be able to consume the Json metadata document by implementing a parser. > This issue could be implemented by a Student who takes part in the GSoC. The > metadata document is already available as an xml format which could give a > student a very good entry point to learn more about OData and the Olingo > library. Learning opportunities would be about Json payload creation as well > as parsing of Json payloads. This would also include understanding the latest > OData V4 specification. If you are interested comment this issue or write a > mail to dev@olingo.apache.org . > Sources: > Olingo Website: http://olingo.apache.org/ > OData.org: http://www.odata.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1293) Srid is not exposed by the MetadataDocument Serializers
[ https://issues.apache.org/jira/browse/OLINGO-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626133#comment-16626133 ] Steven Hawkins commented on OLINGO-1293: See https://github.com/apache/olingo-odata4/pull/32 > Srid is not exposed by the MetadataDocument Serializers > --- > > Key: OLINGO-1293 > URL: https://issues.apache.org/jira/browse/OLINGO-1293 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Assignee: Ramesh Reddy >Priority: Major > > Property level srid values are not exposed in the metadata. Given > OLINGO-1292 this makes it impossible to determine the srid when using json > results. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OLINGO-1292) Json Serialization of geometry value does not allow for an SRID
[ https://issues.apache.org/jira/browse/OLINGO-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1292: Assignee: Ramesh Reddy > Json Serialization of geometry value does not allow for an SRID > --- > > Key: OLINGO-1292 > URL: https://issues.apache.org/jira/browse/OLINGO-1292 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Assignee: Ramesh Reddy >Priority: Major > > Due to > [https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/server-core/src/main/java/org/apache/olingo/server/core/serializer/json/ODataJsonSerializer.java#L991] > an srid cannot be associated with a value - even if it's the default 0 or > 4326 for geometry or geography respectively. > Looking at the reference service output > [https://services.odata.org/TripPinRESTierService/Airports] > the srid is associated, and it's already part of the client serialization > logic > [https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/client-core/src/main/java/org/apache/olingo/client/core/serialization/JsonGeoValueSerializer.java#L42] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OLINGO-1293) Srid is not exposed by the MetadataDocument Serializers
[ https://issues.apache.org/jira/browse/OLINGO-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1293: Assignee: Ramesh Reddy > Srid is not exposed by the MetadataDocument Serializers > --- > > Key: OLINGO-1293 > URL: https://issues.apache.org/jira/browse/OLINGO-1293 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Assignee: Ramesh Reddy >Priority: Major > > Property level srid values are not exposed in the metadata. Given > OLINGO-1292 this makes it impossible to determine the srid when using json > results. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OLINGO-1294) Polygon should support multiple interior holes
[ https://issues.apache.org/jira/browse/OLINGO-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1294: Assignee: Ramesh Reddy > Polygon should support multiple interior holes > -- > > Key: OLINGO-1294 > URL: https://issues.apache.org/jira/browse/OLINGO-1294 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Assignee: Ramesh Reddy >Priority: Major > > The Polygon value object is limited to a single interior. It should hold any > number of holes, which is allowed by the grammar > https://docs.oasis-open.org/odata/odata/v4.0/os/abnf/odata-abnf-construction-rules.txt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1292) Json Serialization of geometry value does not allow for an SRID
[ https://issues.apache.org/jira/browse/OLINGO-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625892#comment-16625892 ] Steven Hawkins commented on OLINGO-1292: See https://github.com/apache/olingo-odata4/pull/31 > Json Serialization of geometry value does not allow for an SRID > --- > > Key: OLINGO-1292 > URL: https://issues.apache.org/jira/browse/OLINGO-1292 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Steven Hawkins >Priority: Major > > Due to > [https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/server-core/src/main/java/org/apache/olingo/server/core/serializer/json/ODataJsonSerializer.java#L991] > an srid cannot be associated with a value - even if it's the default 0 or > 4326 for geometry or geography respectively. > Looking at the reference service output > [https://services.odata.org/TripPinRESTierService/Airports] > the srid is associated, and it's already part of the client serialization > logic > [https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/client-core/src/main/java/org/apache/olingo/client/core/serialization/JsonGeoValueSerializer.java#L42] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
