[
https://issues.apache.org/jira/browse/OLINGO-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Stolzenberger updated OLINGO-929:
----------------------------------------
Description:
Hi,
I'm using Olingo version 2.0.6 with JPA adapter. I'm sending an update entry
request via HTTP POST which fails with this error message:
{code}
<?xml version='1.0' encoding='UTF-8'?><error
xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code/><message
xml:lang="en">Could not match segment:
'RootEntity1s('734f14ef-960e-463f-bc73-983147f94c6d')/ItemEntity1_1Details'.</message></error>
{code}
This is the relevant payload- snipped that causes the problem:
{code}
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<atom:entry ...>
...
<m:properties>
...
</atom:content>
<atom:id>https://hepindustrymobility1-industrymobility2.neo.ondemand.com:443/com.sap.icmobile.demo.application/odata/referenceservice/RootEntity1s('734f14ef-960e-463f-bc73-983147f94c6d')</atom:id>
<atom:link href="RootEntity1s('734f14ef-960e-463f-bc73-983147f94c6d')"
rel="edit" title="RootEntity1"/>
...
</atom:entry>
{code}
When removing the link from the payload than this message is processed properly.
Attached is the corresponding error stack trace.
I tested this payload on a SAP Netweaver Gateway system where these deferred
links does not cause any problem.
Regards,
Tobias
was:
Hi,
I'm using Olingo version 2.0.6 with JPA adapter. I'm sending an update entry
request via HTTP POST which fails with this error message:
{code}
<?xml version='1.0' encoding='UTF-8'?><error
xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code/><message
xml:lang="en">Could not match segment:
'RootEntity1s('734f14ef-960e-463f-bc73-983147f94c6d')/ItemEntity1_1Details'.</message></error>
{code}
This is the relevant payload- snipped that causes the problem:
{code}
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<atom:entry ...>
...
<m:properties>
...
</atom:content>
<atom:id>https://hepindustrymobility1-industrymobility2.neo.ondemand.com:443/com.sap.icmobile.demo.application/odata/referenceservice/RootEntity1s('734f14ef-960e-463f-bc73-983147f94c6d')</atom:id>
<atom:link href="RootEntity1s('734f14ef-960e-463f-bc73-983147f94c6d')"
rel="edit" title="RootEntity1"/>
...
</atom:entry>
{code}
When removing the link from the payload than this message is processed properly.
Attached is the corresponding error stack trace.
Regards,
Tobias
> Update Entry fails when containing deferred links
> -------------------------------------------------
>
> Key: OLINGO-929
> URL: https://issues.apache.org/jira/browse/OLINGO-929
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 2.0.6
> Reporter: Tobias Stolzenberger
> Attachments: UpdateEntryErrorStacktrace.txt
>
>
> Hi,
> I'm using Olingo version 2.0.6 with JPA adapter. I'm sending an update entry
> request via HTTP POST which fails with this error message:
> {code}
> <?xml version='1.0' encoding='UTF-8'?><error
> xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code/><message
> xml:lang="en">Could not match segment:
> 'RootEntity1s('734f14ef-960e-463f-bc73-983147f94c6d')/ItemEntity1_1Details'.</message></error>
> {code}
> This is the relevant payload- snipped that causes the problem:
> {code}
> <?xml version="1.0" encoding="utf-8" standalone="yes"?>
> <atom:entry ...>
> ...
> <m:properties>
> ...
> </atom:content>
> <atom:id>https://hepindustrymobility1-industrymobility2.neo.ondemand.com:443/com.sap.icmobile.demo.application/odata/referenceservice/RootEntity1s('734f14ef-960e-463f-bc73-983147f94c6d')</atom:id>
> <atom:link href="RootEntity1s('734f14ef-960e-463f-bc73-983147f94c6d')"
> rel="edit" title="RootEntity1"/>
> ...
> </atom:entry>
> {code}
> When removing the link from the payload than this message is processed
> properly.
> Attached is the corresponding error stack trace.
> I tested this payload on a SAP Netweaver Gateway system where these deferred
> links does not cause any problem.
> Regards,
> Tobias
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)