[OLINGO-929] Update Entry fails when containing deferred links

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: V2 2.0.6
• Fix Version/s: V2 2.0.7
• Component/s: odata2-core
• Assignee: mibo
• Reporter: Tobias Stolzenberger
• Created: 06/Apr/16 11:43
• Updated: 21/Apr/16 19:25
• Resolved: 21/Apr/16 19:25

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:

<?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>

This is the relevant payload- snipped that causes the problem:

<?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>

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

Issue Links

• is a clone of: OLINGO-926 Batch Request fails if request line is absolute