You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Gastón Brito (Jira)" <ji...@apache.org> on 2019/09/11 16:48:00 UTC

[jira] [Created] (OLINGO-1396) Olingo2 throw an exception when a key is null on a POST operation (which will be autogenerated)

Gastón Brito created OLINGO-1396:
------------------------------------

             Summary: Olingo2 throw an exception when a key is null on a POST operation  (which will be autogenerated) 
                 Key: OLINGO-1396
                 URL: https://issues.apache.org/jira/browse/OLINGO-1396
             Project: Olingo
          Issue Type: Bug
          Components: odata2-core
            Reporter: Gastón Brito


There are some cases, where a field is marked as non-nullable in the EDM (Nullable=false), just because it won't be null on GET or PATCH operations. But in POST operation, that field is automatically generated with the target system, like a sequential key (it's happened in a lot of cases on SAP S4Hana system). 

With those cases, Olingo2-core is throwing an exception in the following line: [https://gitbox.apache.org/repos/asf?p=olingo-odata2.git;a=blob;f=odata2-lib/odata-core/src/main/java/org/apache/olingo/odata2/core/edm/AbstractSimpleType.java;h=e78e8b653cc3d76245883f0487dedb58ca54cd0b;hb=refs/heads/master#l104] 

 

Is it possible to remove that validation?

 

Thanks in advance, regards



--
This message was sent by Atlassian Jira
(v8.3.2#803003)