jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Strasser (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JCR-170) VirtualItemStates of node types definitions not accessible with uuid
Date Sat, 16 Jul 2005 16:12:13 GMT
     [ http://issues.apache.org/jira/browse/JCR-170?page=all ]
Tobias Strasser closed JCR-170:

    Resolution: Invalid

all the virtually mapped nodestates are initialized on startup or on registration of new nodetypes.
the mechanism is a bit obscure, but the createNodeTypeState() method calls the createNodeState()
method of the AbstractVISProvider , which puts the newly created state into its cache. the
cache is basically implemented with a soft-ref hashmap, so the items could disapear. to prevent
this, they are also added as hard reference to the parent node state. imo, the internalGetNodeState()
and internalHasNodeState() should never be called since the items should retain in the cache
for ever.
as soon as the cache implementation in the AbstractVISProvider changes, we might reconsider
this issue.

> VirtualItemStates of node types definitions not accessible with uuid
> --------------------------------------------------------------------
>          Key: JCR-170
>          URL: http://issues.apache.org/jira/browse/JCR-170
>      Project: Jackrabbit
>         Type: Bug
>   Components: nodetype
>  Environment: svn revision: 219171
>     Reporter: Marcel Reutegger
>     Assignee: Tobias Strasser
>     Priority: Minor
>      Fix For: 1.0

> The VirtualNodeTypeStateProvider that maps node type definitions into the workspace under
/jcr:system/jcr:nodeTypes does not implement the methods:
> - internalGetNodeState(NodeId id)
> - internalHasNodeState(NodeId id)
> This has the effect that ItemStates that reflect node type definitions are not accessible
directly with their uuid.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message