[
https://issues.apache.org/jira/browse/OLINGO-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874106#comment-16874106
]
Matthias Günter commented on OLINGO-1322:
-----------------------------------------
Hi [~ramya.vasanth] and [~archanarai],
since your update of this commit:
[https://github.com/apache/olingo-odata2/commit/7284619af7cdc55d0d1b01505bc27f7df600f4b8]
it is tagged as 2.0.11. Unfortunely the revert of the commit is not tagged as
2.0.11:
[https://github.com/apache/olingo-odata2/commit/a941f16db247d3988d6e94f4a9c8775ccb4f0884]
. When downloading the dependency via maven
{code:java}
<dependency>
<groupId>org.apache.olingo</groupId>
<artifactId>olingo-odata2-core</artifactId>
<version>2.0.11</version>
<scope>compile</scope>
</dependency>
{code}
we get the UriParser where an empty string is not allowed > our web application
fails on some points. How should we proceed?
Best regards,
Matthew :)
> ODATA V2.0: An empty string validation in UriParser
> ---------------------------------------------------
>
> Key: OLINGO-1322
> URL: https://issues.apache.org/jira/browse/OLINGO-1322
> Project: Olingo
> Issue Type: Improvement
> Components: odata2-core
> Affects Versions: V2 2.0.10
> Reporter: Archana Rai
> Assignee: Archana Rai
> Priority: Minor
> Fix For: V2 2.0.11
>
>
> An empty string does not correspond to any id.
> For e.g. An odata update request on Products, but with a empty string for the
> key-value:
> MERGE Products('')
> This should get validated while uri validation itself rather than getting
> validated in the serializers.
> This will better for performance as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
