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 Thu, 08 Feb 2007 13:31:14 GMT

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

Anton Slutsky commented on JCR-322:

All good points, Stefan.  I'll address them.

The only problem I'm having is, if we are not to expose a getSystemSession() on RepositoryImpl,
a slight complication arises.  SystemSession class is package private.  SessionImpl constructors
are protected and I cant use SessionImpl anyway because I need to be able to get around the
access manager.  The only way I see of getting a low level session to check for things in
workspaces is to subclass SessionImpl in org.apache.jackrabbit.core.notetype package and use
this new class as my session implementation to get around protection levels.  But thats just
silly! :-)  Something's gotta give.  My suggestion here would be to add a SessionManager interface,
which could be used to create various types of sessions.  But again, thats just a though.
 If you guys know of a better way, do let me know.

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