[
https://issues.apache.org/jira/browse/OLINGO-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641499#comment-16641499
]
Peter Lawrence commented on OLINGO-1303:
----------------------------------------
<<Is that still true? So Olingo v4 does not support dynamic properties? What is
the isOpenType=true setting used for then?>>
That is my observation, but I am also trying to understand why support has been
added for isOpenType=true
With reference to the link you supplied ...
<<If you only want these dynamic properties to be in the payload as a
workaround you can use your own deserializer and serializer.>>
I am thinking that rewriting the serializer will be the only option
<< If you want to address these dynamic properties within the URL then there is
no workaround as the URL is tightly checked against the metadata as well.>>
This I can understand so I am assuming the semantics that $select=* would allow
inclusion of all dynamic properties. I am unclear what the OData standard says
about referencing open properties in a request.
> Serializing OpenType dynamic properties
> ---------------------------------------
>
> Key: OLINGO-1303
> URL: https://issues.apache.org/jira/browse/OLINGO-1303
> Project: Olingo
> Issue Type: Question
> Components: odata2-core
> Affects Versions: (Java) V4 4.5.0
> Reporter: Peter Lawrence
> Priority: Blocker
>
> Olingo 4.5.0 includes openType in the metadata, however I cannot see how to
> enable serializing of properties that are not included in the metadata
> (dynamic properties).
> It appears that the results serializer will only serialize those properties
> that are declared in the metadata. ... or am I missing something?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
