jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-771) Make the CND files AUTOMATICALLY loaded from its natural place: /repository/nodetypes
Date Thu, 01 Mar 2007 10:44:50 GMT

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


jackrabbit's internal persistent representation of the registered custom 
node type definitions (<rep home>/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:

> 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
> Both are currenlty boilerplate code and lot of newcomers (like myself :-) struggle with
> 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.

View raw message