[
https://issues.apache.org/jira/browse/JCR-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487771
]
Jukka Zitting commented on JCR-836:
-----------------------------------
Such a feature would IMHO be best implemented with customizable startup scripts
as proposed in JCR-324. Alternatively we should have a node type tool like the
one included in Day's Content Explorer that could be used by an administrator
to register new node types.
See also JCR-771 for the same feature request that was resolved as Won't Fix.
I'm inclined to do the same for this issue unless the objections are countered.
> Configuration of nodetypes vs programming of nodetypes
> ------------------------------------------------------
>
> Key: JCR-836
> URL: https://issues.apache.org/jira/browse/JCR-836
> Project: Jackrabbit
> Issue Type: New Feature
> Components: nodetype
> Affects Versions: 0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3
> Reporter: Darren Hartford
>
> Mandating that you must use programming to define/install nodeTypes is very
> limiting. Recommend allowing the use of a CND configuration folder that is
> read on start-up to configure nodeTypes through CND text files without java
> programming.
> There used to be a repository/nodetype folder that contained XML definitions,
> but those did not necessarily get read in without java programming. Follow
> through with the repository/nodetype folder for CND text files (and/or
> workspace/nodetype folder) that can be loaded on-startup without requiring
> programming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
