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-322) Support node type modification and removal
Date Fri, 09 Feb 2007 09:08:05 GMT

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

Stefan Guggisberg commented on JCR-322:
---------------------------------------

> Anton Slutsky commented on JCR-322:
> -----------------------------------
> 
> Like I said, extending SessionImpl in the nodetype package is an option.  The issue here
is not my inability to extend a class and copy code from the org/apache/jackrabbit/core/SystemSession.java
file.  Its the silliness of such an approach.  Basically, what will happen is, we'll be duplicating
the SystemSession code just for the sake of duplicating it.  I dont believe this is a good
thing at all.


i absolutely agree with anton. publicly exposing the system session on the other hand would
be an unacceptable security risk. 

currently there's *one* internal system session per workspace. sharing this system session
might cause other potential issues like e.g. concurrency (since java.jcr.Session is per definition
not threadsafe).

we have to come up with some way of strictly-internally-only exposing a System Session factory.
this would btw also require to rewrite some of  the workspace housekeeping code (idle workspaces,
i.e. those with no logged in sessions, are automatically shutdown) since it  would be more
difficult to determine whether a workspace is idle or not.

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


Mime
View raw message