jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2303) PredefinedNodeTypeTest too strict
Date Thu, 17 Sep 2009 20:00:57 GMT

    [ https://issues.apache.org/jira/browse/JCR-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756741#action_12756741
] 

Marcel Reutegger commented on JCR-2303:
---------------------------------------

A reminder that jackrabbit-core and jackrabbit-spi2jcr currently mark org.apache.jackrabbit.test.api.nodetype.PredefinedNodeTypeTest#testResource
as known issue. Those can be removed again once this issue is fixed.

> PredefinedNodeTypeTest too strict
> ---------------------------------
>
>                 Key: JCR-2303
>                 URL: https://issues.apache.org/jira/browse/JCR-2303
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-tests
>            Reporter: Marcel Reutegger
>         Attachments: JCR-2303.patch
>
>
> 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.

-- 
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