jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2065) use the internal CND file for builtin nodetypes
Date Wed, 08 Apr 2009 14:01:15 GMT

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

Tobias Bocanegra resolved JCR-2065.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0

added missing node types to the CND file and removed the builtin xml one.
note that the custom node types are still stored in the custom_nodetypes.xml

> use the internal CND file for builtin nodetypes
> -----------------------------------------------
>
>                 Key: JCR-2065
>                 URL: https://issues.apache.org/jira/browse/JCR-2065
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: nodetype
>    Affects Versions: 2.0.0
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>             Fix For: 1.6.0
>
>
> the jackrabbit node type registry is reading the built in node types from a XML file.
> since the CND (compact node type definition notation) is now specified by jsr283,
> i would like to drop the builtin .xml file and read the builtin node typesonly from the
.cnd file.
> this certainly helps the developers. furthermore, all the node types in jsr283 are now
speced
> in CND, and converting them to XML is a pain and error prone.

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