Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Message-ID: <1801682842.1131640988576.JavaMail.jira@ajax.apache.org>
Date: Thu, 10 Nov 2005 17:43:08 +0100 (CET)
From: "Stefan Guggisberg (JIRA)" <jira@apache.org>
To: jackrabbit-dev@incubator.apache.org
Subject: [jira] Closed: (JCR-60) primaryItemName is not inherited
In-Reply-To: <145418308.1110360053026.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JCR-60?page=all ]
     
Stefan Guggisberg closed JCR-60:
--------------------------------


closing resolved issue

> primaryItemName is not inherited
> --------------------------------
>
>          Key: JCR-60
>          URL: http://issues.apache.org/jira/browse/JCR-60
>      Project: Jackrabbit
>         Type: Bug
>   Components: API
>  Environment: jackrabbit r156508
>     Reporter: Tobias Strasser
>     Assignee: Peeter Piegaze

>
> if no primaryItemName is defined for a nodetype definition, it should be inherited from one of the supertypes. the spec is unclear about this, though it seems to be the natural behaviour.
> for example when extending nt:resource, the subtype should not be force to redefine the jcr:data as primaryItemName.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira