jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Slutsky (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-322) Support node type modification and removal
Date Mon, 12 Feb 2007 13:26:06 GMT

    [ https://issues.apache.org/jira/browse/JCR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472288

Anton Slutsky commented on JCR-322:

I'm thinking, there are basically two alternatives here.   Either we expose the SystemSession
somehow or we bite the bullet and recurse on each workspace checking for the node type.  It
could be documented in unregister() that the operation does a slow check and may take time.

There is another concern however.  A mechanism has to be developed to figure out which repository
user should be allowed to delete node types.  From what I can see, it looks like any session
can call unregister() on a node type.  It could be a problem.  Even if no content exist for
a given node type (which would have to be true to be able to unregister()), node types themselves
are important.  In our application, we have custom node type definitions defining a node structure
expected by various JSP templates.  Removing a type, even if no content has yet been created,
is a big deal.  

> Support node type modification and removal
> ------------------------------------------
>                 Key: JCR-322
>                 URL: https://issues.apache.org/jira/browse/JCR-322
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: nodetype
>    Affects Versions: 0.9, 1.0
>            Reporter: Jukka Zitting
>         Attachments: nodetyperegistry.patch, OKMSystemSession.java
> There is currently no way to modify or remove registered node types. The existing reregister
and unregister methods in NodeTypeRegistry  throw "not yet implemented" exceptions for anything
else than trivial node type changes.
> JSR 283 is working on an node type management API that we should ultimately implement.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message