[
https://issues.apache.org/jira/browse/OLINGO-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan V.A updated OLINGO-459:
-------------------------------
Assignee: Christian Amend (was: Chandan V.A)
> JPA Batch does not support creating new instance and link this to an existing
> one in one change set
> ---------------------------------------------------------------------------------------------------
>
> Key: OLINGO-459
> URL: https://issues.apache.org/jira/browse/OLINGO-459
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core, odata2-jpa
> Affects Versions: V2 2.0.0
> Reporter: Björn Wagner
> Assignee: Christian Amend
>
> Steps necessary to reproduce this:
> (1) Create new instance (including client generated GUID primary key)
> (2) Link this instance to another already existing instance of a different
> entity
> While the exact same requests work fine when executed as single requests, the
> second one fails when executed in batch. I debugged into the olingo code and
> the exception is thrown at
> org.apache.olingo.odata2.jpa.processor.core.access.data.JPALink:276
> It looks like the wrong UriInfo is passed into that function. At first
> glance, this function receives the UriInfo from the outer batch request
> instead of the info for the link request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
