Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 34699 invoked from network); 1 Mar 2007 10:45:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Mar 2007 10:45:13 -0000 Received: (qmail 38383 invoked by uid 500); 1 Mar 2007 10:45:22 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 38052 invoked by uid 500); 1 Mar 2007 10:45:20 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 38034 invoked by uid 99); 1 Mar 2007 10:45:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 02:45:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 02:45:11 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CC42F714207 for ; Thu, 1 Mar 2007 02:44:50 -0800 (PST) Message-ID: <975588.1172745890834.JavaMail.jira@brutus> Date: Thu, 1 Mar 2007 02:44:50 -0800 (PST) From: "Stefan Guggisberg (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-771) Make the CND files AUTOMATICALLY loaded from its natural place: /repository/nodetypes In-Reply-To: <30575665.1172589006044.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476886 ] Stefan Guggisberg commented on JCR-771: --------------------------------------- > i think, the big problem when developing with JR is to manage the nodetypes. > before we had the CND, you had to modify the custom nodetype.xml by > hand. of course you can use the CND importer now, but it would be very > handy, if the custom nodetypes would be written/read as CND as well. clarification: jackrabbit's internal persistent representation of the registered custom node type definitions (/nodetypes/custom_nodetypes.xml) is an implementation detail and was never meant to be externally modified! if you do so you risk corrupting your repository. this has been repeatedly pointed out on the list. btw: you wouldn't expect to be able to manually edit e.g. a tablespace file of an oracle database... since jackrabbit 1.0 you are able to register your node type definitions in either xml or cnd format: http://jackrabbit.apache.org/api-1/org/apache/jackrabbit/core/nodetype/NodeTypeManagerImpl.html#registerNodeTypes(java.io.InputStream,%20java.lang.String) > Make the CND files AUTOMATICALLY loaded from its natural place: /repository/nodetypes > ------------------------------------------------------------------------------------- > > Key: JCR-771 > URL: https://issues.apache.org/jira/browse/JCR-771 > Project: Jackrabbit > Issue Type: Improvement > Components: nodetype > Affects Versions: 1.2.2 > Environment: any > Reporter: Wolf Benz > Priority: Minor > Fix For: 1.3 > > > Currently there is no AUTOMATIC support for the predefined custom node type files in CND format. > They have to be loaded manually, same as the fact as for every getSession() the namespaces are to be registered... > I think these 2 issues could best be solved together: > It would be a tremendous improvement if we could just put the cnd file inside /repository/nodetypes. Such file starts by declaring the namepsaces anyway so it would also make the tedious NS registration redundant. > Both are currenlty boilerplate code and lot of newcomers (like myself :-) struggle with it. > For more info, please have a look at this thread on the JR maling list: "Namespaces - questions" (posted by myself) > Wolf -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.