jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-1140) NodeId for root node should not be hardcoded in jcr2spi
Date Fri, 28 Sep 2007 11:18:50 GMT

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

Michael Dürig commented on JCR-1140:

> for the second one (spi2jcr): that wrong. but can you please open a different issue for
See https://issues.apache.org/jira/browse/JCR-1147

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

View raw message