You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/11/26 07:18:36 UTC

[jira] [Commented] (OLINGO-44) $expand doesn't work for several projections of a child navigation property

    [ https://issues.apache.org/jira/browse/OLINGO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832351#comment-13832351 ] 

ASF subversion and git services commented on OLINGO-44:
-------------------------------------------------------

Commit d4df5ccd3ddd63d6add59d55d92265b9416e97d0 in branch refs/heads/master from [~chandan.v.a]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-olingo-odata2.git;h=d4df5cc ]

[OLINGO-44] Fix for $expand

Signed-off-by: Chandan V A <ch...@sap.com>


> $expand doesn't work for several projections of a child navigation property
> ---------------------------------------------------------------------------
>
>                 Key: OLINGO-44
>                 URL: https://issues.apache.org/jira/browse/OLINGO-44
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-jpa
>    Affects Versions: V2 1.0.0, V2 1.1.0
>            Reporter: Georgi
>            Assignee: Chandan V.A
>            Priority: Critical
>
> Consider the following JPA model with one-to-many CMRs:
> X(1) -> (N) A (1) -> (N) B (1) -> (N) C
> X(1) -> (N) A (1) -> (N) D (1) -> (N) E
> To get the complete model for X inline, I use $expand:
> /X(1)/$expand=A/B/C,A/D/E
> However, this yields a NullPointerException in JpaExpandCallback:108
> Debugging the code shows that the reason is that the data constructed for response is missing anything but one of the paths provided in the $expand list.
> I think that the reason is the algorithm of parse2EdmNavigationValueMap, which takes as input a valid navigationPropertyList, but fails to produce and adequate navigation properties map for this case. That is probably due to the matching navigation property names (ADetails), which effectively overwrites previous entries. That leaves the system in an inconsistent state and we end up with the NPE in JpaExpandCallback.



--
This message was sent by Atlassian JIRA
(v6.1#6144)