[
https://issues.apache.org/jira/browse/CMIS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629552#comment-14629552
]
Jens Hübel commented on CMIS-921:
---------------------------------
Sorry, but I do not quite get what the problem is.
TypeValidator.typeContainsPropertyWithQueryName is tolerant that's true and
intended.
ColumnReference is a class that refers to a single property definition. There
is no lookup function of any kind in this class that could be case insensitive
or not. ColumnReference.getTypeDefinition() just returns the type definition of
this property definition and is a simple getter.
Can you describe your use case? Is your ColumnReference object perhaps already
in an invalid state because of some case discrepancy happening before? I need
more info which lookup is actually failing to fix this.
I assume that case insensitive would be the preferred way to handle match.
Correct?
> property query name case inconsistency
> --------------------------------------
>
> Key: CMIS-921
> URL: https://issues.apache.org/jira/browse/CMIS-921
> Project: Chemistry
> Issue Type: Bug
> Components: opencmis-server
> Affects Versions: OpenCMIS 0.13.0
> Reporter: Michael Brackx
> Assignee: Jens Hübel
>
> Inconsistency in the handling of property query name case.
> Querying for a property with the incorrect case, passes the type validator,
> but then later on its columreference has no property definition.
> TypeValidator.typeContainsPropertyWithQueryName is tolerant, yet
> ColumnReference.getTypeDefinition is strict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
