Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <2123906999.1245320347709.JavaMail.jira@brutus>
Date: Thu, 18 Jun 2009 03:19:07 -0700 (PDT)
From: "Tobias Bocanegra (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-2066) NodeTypeRegistry could auto-subtype
 from nt:base
In-Reply-To: <1396863531.1239200593118.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tobias Bocanegra resolved JCR-2066.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

fixed in revision 786003

> NodeTypeRegistry could auto-subtype from nt:base
> ------------------------------------------------
>
>                 Key: JCR-2066
>                 URL: https://issues.apache.org/jira/browse/JCR-2066
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> this is basically a copy of JCR-433, which was fixed but somehow sneaked in again:
> when tying to register a (primary) nodetype that does not extend from nt:base the following error is
> thrown:
> "all primary node types except nt:base itself must be (directly or indirectly) derived from nt:base"
> since the registry is able to detect this error, it would be easy to auto-subtype all nodetypes from nt:base. 
> imo it's pointless to explicitly add the nt:base to every superclass set. as an analogy, you don't need to 
> 'extend from java.lang.Object' explicitly - the compiler does that automatically for your.

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