You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Björn Wagner (JIRA)" <ji...@apache.org> on 2014/10/13 11:49:34 UTC
[jira] [Created] (OLINGO-459) JPA Batch does not support creating
new instance and link this to an existing one in one change set
Björn Wagner created OLINGO-459:
-----------------------------------
Summary: 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-jpa
Affects Versions: V2 2.0.0
Reporter: Björn Wagner
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)