You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2007/10/02 15:42:50 UTC

[jira] Commented: (JCR-1140) NodeId for root node should not be hardcoded in jcr2spi

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

angela commented on JCR-1140:
-----------------------------

ok. it seems that this issue can be resolved, since it turns out to be a misunderstanding due to missing 
documentation in the spi.

i added some more javadoc to IdFactory with rev. 581235  


> NodeId for root node should not be hardcoded in jcr2spi
> -------------------------------------------------------
>
>                 Key: JCR-1140
>                 URL: https://issues.apache.org/jira/browse/JCR-1140
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: SPI
>            Reporter: Michael Dürig
>
> org.apache.jackrabbit.jcr2spi.hierarchy.NodeEntryImpl.getId() always returns idFactory.createNodeId((String) null, Path.ROOT) for the root node although a repository might want to reference the root node by UUID. NodeId.getId() breaks the contract of org.apache.jackrabbit.spi.ItemId which for this case states: "The item can not be identified with a unique ID and none of its ancestors can be identified with a unique ID. The item is identified by an absolute path".
> I suggest to change the implementation such that when NodeId.getId() needs to return the NodeId of the root node a round trip to org.apache.jackrabbit.spi.RepositoryService.getRootId() is done. 

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