jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1135) boolean value constraints exposed in custom format
Date Fri, 17 Oct 2008 10:45:44 GMT

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

Jukka Zitting updated JCR-1135:

    Component/s: jackrabbit-core

> boolean value constraints exposed in custom format
> --------------------------------------------------
>                 Key: JCR-1135
>                 URL: https://issues.apache.org/jira/browse/JCR-1135
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, nodetype
>            Reporter: Julian Reschke
>            Priority: Minor
> It seems that Jackrabbit currently exposes boolean value constraints in a non-compliant
> For a constraint of "true", JSR-170 (6.7.16) IMHO requires a range notation such as:
>  [ true, true ]
> JSR-283 on the other hand currently states that constraints on boolean values are not
exposed at all.
> Jackrabbit in fact exposes the constraint as 
>   true
> which of course makes a lot of sense. I think both JSR-170 and JSR-283 should be fixed
to require this behavior.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message