[
https://issues.apache.org/jira/browse/OLINGO-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Kobler-Morris closed OLINGO-276.
-------------------------------------
Resolution: Fixed
> Convert the DataJS (javascript codes) from OData Protocol V3 to V4 format
> -------------------------------------------------------------------------
>
> Key: OLINGO-276
> URL: https://issues.apache.org/jira/browse/OLINGO-276
> Project: Olingo
> Issue Type: New Feature
> Components: odata4-client-JS
> Environment: All
> Reporter: Bing Li
> Assignee: Bing Li
>
> The Data.JS codes on
> https://git-wip-us.apache.org/repos/asf/olingo-odata4-js.git are the legacy
> odata protocol V3 codes. It needs to convert to V4. The major works should
> be:
> 1. Remove all the Json verbose logic, make the DataJS accepted and
> returned javascript object be in Json light format. (Since Json verbose has
> been completely removed on V4, making the javascript object returned by
> DataJS in json verbose format doesn’t make sense any more. )
> 2. Add the supports for parsing and setting the changed and new added
> headers in the request/response.
> 3. Parse OData V4 Metadata payload.
> 4. Make the DataJS cache and storage components work.
> 5. Batch payload parser and serializer. (Note: “Serializer” means
> serializing javascript object to the string payload which could be posted to
> OData service side, while “Parser” means converting the odata payload string
> to javascript object.)
> 6. Json light Payload parser and serializer.
> Since OData protocol contains some data types which could not be handled by
> javascript directly (e.g. EDM.Duration, Edm.DateTime, Edm.Float, Edm.Decmal,
> Edm.Int64 and etc.) and the non-metadata/mini-metadata payloads are lack of
> type information, we need to implement parsing/serializing each kind of odata
> payload and handle these types specifically. Here are the possible works:
> • Parse json light feeds, entity, complex properties, navigation
> properties, singleton, containment, function, action, enum and etc. payloads.
> This issue only coverts 1-5. For 6, the json parser ans serializer will use
> the javascript build-in one in the current stage.
> • Serialize json light feeds, entity, primitive properties,
> navigation properties, singleton, containment, function, action, enum and
> etc. payloads.
> • Special handles in data in format Edm.Duration, Edm.DateTime,
> Edm.Decimal, Edm.Int64 and etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
