[JCR-1135] boolean value constraints exposed in custom format

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: jackrabbit-core, nodetype
• Assignee: Unassigned
• Reporter: Julian Reschke
• Created: 16/Sep/07 10:26
• Updated: 17/Oct/08 10:43

Description

It seems that Jackrabbit currently exposes boolean value constraints in a non-compliant way.

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.