You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Chandan V.A (JIRA)" <ji...@apache.org> on 2013/10/30 10:14:26 UTC

[jira] [Assigned] (OLINGO-51) Cannot create an Entry that is related to another one implicitly through the relationship implied in the URL

     [ https://issues.apache.org/jira/browse/OLINGO-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chandan V.A reassigned OLINGO-51:
---------------------------------

    Assignee: Chandan V.A

> Cannot create an Entry that is related to another one implicitly through the relationship implied in the URL
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: OLINGO-51
>                 URL: https://issues.apache.org/jira/browse/OLINGO-51
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-jpa
>    Affects Versions: 1.0.0, 1.1.0
>            Reporter: Georgi
>            Assignee: Chandan V.A
>            Priority: Blocker
>
> Trying to create an entry with the same setup as described in https://issues.apache.org/jira/browse/OLINGO-49 created the entry but failed to set the relation, thus leaving the model in inconsistent state.
> Sample request:
> HTTP POST <path>/As(1)/b
> "{\"aId\":0}" 
> As a result the a.b is null.
> The createView's startEntitySet property and the id in the URI are ignored and then a normal create for the depending Entiity is performed without considering the context of its owner.
> For use case reference: http://www.odata.org/documentation/odata-v2-documentation/operations/#24_Creating_new_Entries
> , the section that describes how to  to create an Entry that is related to another one implicitly through the relationship implied in the URL.



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