jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2146) PropertyDefinition.getAvailableQueryOperators does not return qualified names
Date Fri, 12 Jun 2009 08:52:07 GMT

     [ https://issues.apache.org/jira/browse/JCR-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

angela updated JCR-2146:
------------------------

    Description: 
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.




  was:
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 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.





> 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
>    Affects Versions: 2.0-alpha1
>            Reporter: angela
>             Fix For: 2.0.0
>
>
> 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.


Mime
View raw message