[JCRTCK-5] PredefinedNodeTypeTest too strict

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.1
• Assignee: Unassigned
• Reporter: Marcel Reutegger
• Created: 14/Sep/09 11:32
• Updated: 14/Oct/09 14:31
• Resolved: 21/Sep/09 14:43

Description

Description copied from: https://jsr-283.dev.java.net/issues/show_bug.cgi?id=808

This test check whether the standard JCR node types are exposed as defined in the
spec. Some of the checks are too strict because certain aspects of a standard node
type can be implementation variant:

• 3.7.16.1.2 "Additions to the Hierarchy": additional super types are allowed, but
  the test currently fails if a standard node type has more than the specified super
  types.

• 3.7.16.1.4 "Variant Attributes": some metadata mixins defined in JSR 283 have
  variant OPV settings and protected flags, but the test currently fails if an
  implementation differs from the standard settings/flags.

Issue Links

• is related to: JCR-2170 Remove PropDefId and NodeDefId