[
https://issues.apache.org/jira/browse/OLINGO-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15473958#comment-15473958
]
Steven Hawkins commented on OLINGO-1009:
----------------------------------------
Cycle detection was not included in this patch, and no real max is enforced, so
yes such a situation would be an issue. There are two solutions - either make
the serialization aware of an explicit max. Or without an explicit max, you
could just detect a cycle of object references - as having a cycle expanded in
different entity objects could just be assumed to be part of the desired
expansion level.
> Provide serilization support for $levels with $expand
> -----------------------------------------------------
>
> Key: OLINGO-1009
> URL: https://issues.apache.org/jira/browse/OLINGO-1009
> Project: Olingo
> Issue Type: New Feature
> Components: odata4-server
> Affects Versions: (Java) V4 4.0.0-beta-01
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: (Java) V4 4.3.0
>
>
> Currently Olingo parses the query with $expand with $levels construct,
> however if the payload contains the nesting of the entities, it does not
> serialize to the defined $levels
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
