Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C4318200CDF for ; Wed, 26 Jul 2017 07:54:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C2CD9166110; Wed, 26 Jul 2017 05:54:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 13A781660FF for ; Wed, 26 Jul 2017 07:54:03 +0200 (CEST) Received: (qmail 61848 invoked by uid 500); 26 Jul 2017 05:54:03 -0000 Mailing-List: contact dev-help@olingo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@olingo.apache.org Delivered-To: mailing list dev@olingo.apache.org Received: (qmail 61828 invoked by uid 99); 26 Jul 2017 05:54:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jul 2017 05:54:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id BB3861A01A5 for ; Wed, 26 Jul 2017 05:54:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id h7lG3tm7kM6D for ; Wed, 26 Jul 2017 05:54:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 41F265FD02 for ; Wed, 26 Jul 2017 05:54:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 71B9BE00A3 for ; Wed, 26 Jul 2017 05:54:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2836F23EFC for ; Wed, 26 Jul 2017 05:54:00 +0000 (UTC) Date: Wed, 26 Jul 2017 05:54:00 +0000 (UTC) From: "Ramya (JIRA)" To: dev@olingo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (OLINGO-1148) Cannot set Nullable property to null value on entity Update MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 26 Jul 2017 05:54:05 -0000 [ https://issues.apache.org/jira/browse/OLINGO-1148?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1148. --------------------------- Resolution: Fixed > Cannot set Nullable property to null value on entity Update > ----------------------------------------------------------- > > Key: OLINGO-1148 > URL: https://issues.apache.org/jira/browse/OLINGO-1148 > Project: Olingo > Issue Type: Bug > Components: odata2-core > Affects Versions: V2 2.0.7, V2 2.0.8 > Reporter: Daniel Horvath > Priority: Critical > > Hello colleagues, > =20 > We have found a strange behaviour in the update process of an entity in O= lingo (2.0.7) OData 2.0. > =20 > When we try to set a property to {color:red}null{color} value it is not s= et but the old value remains. It is caused by the implementation of: > {color:red}setProperty(final Method method, final Object entity, final Ob= ject entityPropertyValue,final EdmSimpleType type, String propertyName){col= or} > method in {color:red}org.apache.olingo.odata2.jpa.processor.core.access.d= ata.JPAEntity{color} class. > =20 > In line 472 there is a check if the entityPropertyValue is null then skip= the setting of the value completely. > The protocol documentation says that we can use the Nullable facet on all= the EDMSimpleType-s because it=E2=80=99s a Commonly Applicable Facet. (Sec= tion 2.2.1.1.1. in https://winprotocoldoc.blob.core.windows.net/productionw= indowsarchives/MC-CSDL/%5bMC-CSDL%5d.pdf) > We think that the setting of null value to a Nullable property should be = allowed. > If you have further questions please feel free to contact me. > Best regards, > Daniel -- This message was sent by Atlassian JIRA (v6.4.14#64029)