[OLINGO-981] Binding operation null on to one

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: (Java) V4 4.2.0
• Fix Version/s: (Java) V4 4.3.0
• Component/s: odata4-server
• Flags: Patch, Important
• External issue URL: http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata03/os/odata-json-format-v4.0-errata03-os-complete.html#_Toc453766651
• Assignee: Ramesh Reddy
• Reporter: Héctor Navarro
• Created: 19/Jul/16 11:31
• Updated: 19/Sep/16 12:42
• Resolved: 27/Jul/16 14:30

Description

Apache Olingo isn't compliant with OData 4 feature "For nullable single-valued navigation properties the value null may be used to remove the relationship".

I believe if the navigation property is a single entity (to one relationship) and it is defined as nullable, it can be null, as sais at OData documentation ("For nullable single-valued navigation properties the value null may be used to remove the relationship.").

As example, we can use org.apache.olingo.server.core.deserializer.json.ODataJsonDeserializerEntityTest.bindingOperationNullOnToOne():

@Test
public void bindingOperationNullOnToOne() throws Exception {
String entityString =
"

{\"PropertyInt16\":32767," + "\"PropertyString\":\"First Resource - positive values\"," + "\"[e-mail]\":null" + "}

";
expectException(entityString, "ETAllPrim",
DeserializerException.MessageKeys.INVALID_NULL_ANNOTATION);
}

I believe that if we define NavPropertyETTwoPrimOne as nullable, it shouldn't throw INVALID_NULL_ANNOTATION exception.