[
https://issues.apache.org/jira/browse/OLINGO-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115827#comment-15115827
]
Michael Bolz commented on OLINGO-837:
-------------------------------------
Hi [~tothgya],
I take a look into the JPA sample and add some test data.
However the {{"parent/parent"}} sample via e.g
"{{http://localhost:8080/SalesOrderProcessing.svc/Customers(202L)?$expand=parent/parent}}"
worked for me.
But I think that for other cases your fix is necessary, hence I [merged it into
master|https://git1-us-west.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=09c0c743a29f07d2d69b04dc0b3c46049f3ac222]
and thank you for the contribution.
Can you please check if it now works for you and close this issue.
Kind Regards,
Michael
> JPAExpandCallBack uses FromRole when validating a navigation property name
> --------------------------------------------------------------------------
>
> Key: OLINGO-837
> URL: https://issues.apache.org/jira/browse/OLINGO-837
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Affects Versions: V2 2.0.5
> Reporter: Gyula Árpád Tóth
> Assignee: Michael Bolz
> Priority: Minor
> Attachments: 0001-OLINGO-837-getNextNavigationProperty-fix.patch
>
>
> Navigation property name validations in JPAExpandCallBack will fail if the
> FromRole is numbered.
> I suggest to cut the numbering from the FromRole and do the compare without
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)