jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerome Banks" <jerome.ba...@gmail.com>
Subject Re: Custom PersistenceManagers - How can I get the path associated with a NodeId?
Date Tue, 24 Jun 2008 17:37:09 GMT
  Thanks for the replies.  The SPI interface is a possibility, but I was
under the impression that it was read-only. That might be the cleanest

   I've been poking around, at noticed that the internal HierarchyManager
class has methods to convert from the ItemId to a  Path.  Is there any
reason not to expose the HierarchyManager, perhaps from the PMContext
object?  Otherwise, is there a way to get the HierarchyManager? It looks
like there is one associated with the Workspace, one with the Session.  Is
there an easy way to access the Workspace or the Session from the PM?

thx ...

On Tue, Jun 24, 2008 at 7:32 AM, Alexander Klimetschek <aklimets@day.com>

> On Tue, Jun 24, 2008 at 4:03 AM, Ard Schrijvers
> <a.schrijvers@onehippo.com> wrote:
> > Nodes in Jackrabbit do not have hierarchical information like its path,
> > but only its parent and its children. Storing path information like you
> > suggest might be handy in some parts, though at the same time makes
> > moving large subtrees almost impossible (at least very cpu and time
> > consuming): currently, moving a subtree of nodes is a very small
> > operation in jackrabbit. If you would store all hierarchical data the
> > way you suggest, you cannot easily move nodes anymore.
> If the underlying storage (here probably a standard file system) has
> its own abstraction (eg. inodes) for the hierarchical information,
> moving subtrees (= folders) is not a problem.
> And it depends on whether moving subtrees is an important use case -
> vs. retrieving nodes by path.
> Regards,
> Alex
> --
> Alexander Klimetschek
> alexander.klimetschek@day.com

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message