[ https://issues.apache.org/jira/browse/JCR-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-2146. ----------------------------------- Resolution: Invalid The corresponding JSR 283 issue has been resolved by turning the query constants into regular strings. Therefore, the current implementation in Jackrabbit is correct. Resolving as invalid. > PropertyDefinition.getAvailableQueryOperators does not return qualified names > ----------------------------------------------------------------------------- > > Key: JCR-2146 > URL: https://issues.apache.org/jira/browse/JCR-2146 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-core, jackrabbit-spi-commons > Reporter: angela > > the latest version of JCR 2.0 defines the jcr:availableQueryOperators > property of the nt:propertyDefinition to be NAME > and the list of possible values is > 'jcr:operatorEqualTo', 'jcr:operatorNotEqualTo', > 'jcr:operatorLessThan', 'jcr:operatorLessThanOrEqualTo', > 'jcr:operatorGreaterThan','jcr:operatorLessThanOrEqualTo', > 'jcr:operatorLike' > (see JSR 283 issue #749) > however, jackrabbit-core currently treats the available query operators as > STRING and returns the expanded form which violates > requirement that all jcr names exposed by API calls must be in qualified form > (prefix:localName). > there is a new open JSR 283 issue (#772) that discusses the reason for the > operator constants being names... resolution of this issue and the > corresponding adjustment of the cnd should be based on that discussion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.