[jira] [Commented] (OLINGO-570) Implement OData Json Metadocument Serializer/Parser
[ https://issues.apache.org/jira/browse/OLINGO-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14362364#comment-14362364 ] haddada commented on OLINGO-570: Hi , i'am a postgraduate computer science student at ESPRIT university, tunisia. I worked in sereveral projects using ( graph search api , google maps … ) and different web technologies . I'am intrested to participate in this project so i started with examining the CSDL json format and the OData trippin sample and it was very helpfull. I wish to implement the parser and the serialiser for the olingo library . 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 Labels: gsoc2015, java, mentor, xml 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 (v6.3.4#6332)
[jira] [Comment Edited] (OLINGO-570) Implement OData Json Metadocument Serializer/Parser
[ https://issues.apache.org/jira/browse/OLINGO-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14362364#comment-14362364 ] haddada edited comment on OLINGO-570 at 3/15/15 1:44 PM: - Hi , i'am a postgraduate computer science student at ESPRIT university, tunisia. I worked in several projects using ( graph search api , google maps … ) and different web technologies . I'am intrested to participate in this project so i started with examining the CSDL json format and the OData trippin sample and it was very helpfull. I wish to implement the parser and the serialiser for the olingo library . was (Author: seif): Hi , i'am a postgraduate computer science student at ESPRIT university, tunisia. I worked in sereveral projects using ( graph search api , google maps … ) and different web technologies . I'am intrested to participate in this project so i started with examining the CSDL json format and the OData trippin sample and it was very helpfull. I wish to implement the parser and the serialiser for the olingo library . 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 Labels: gsoc2015, java, mentor, xml 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 (v6.3.4#6332)
[jira] [Resolved] (OLINGO-592) URL processor fails to get columns from entity
[
https://issues.apache.org/jira/browse/OLINGO-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz resolved OLINGO-592.
-
Resolution: Not a Problem
URL processor fails to get columns from entity
--
Key: OLINGO-592
URL: https://issues.apache.org/jira/browse/OLINGO-592
Project: Olingo
Issue Type: Bug
Components: odata4-server
Affects Versions: (Java) V4 4.0.0-beta-02
Reporter: Frederic Souchu
Assignee: Michael Bolz
How to reproduce:
- add CountEntityCollectionProcessor to Cars producer sample
- navigate to:
http://localhost:8080/odata-server-sample/cars.svc/Cars/$count?$filter=Price
eq 1000
The URI parser returns:
{code}
{error:{code:null,message:The key value 'Price' is invalid.}}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
