[
https://issues.apache.org/jira/browse/JCR-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476686
]
Tobias Bocanegra commented on JCR-771:
--------------------------------------
comment from mailing list:
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.
(at least for people that want to get a quick start with JR)
> 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.
