El vie, 10-03-2006 a las 14:31 +0100, Andreas Hartmann escribió: > Thorsten Scherler wrote: > > Hi all, > > > > it is time to introduce UUID into lenya. Recent threads about mapping, > > external content-dir and document api made one thing cristal clear. We > > need to be more flexible in getting content. > > +1 > > > The last example is moving the meta data from a custom mapping. This > > breaks custom mappings since the file will be written to the location > > defined by the mapper. > > This is not quite true. The location of meta files is now hard-coded > in the DefaultDocument class. This is not nice, but at least there's > a separation between document locations and meta data locations. > > > > The solution is to have *one* place to store meta data and to look it up > > from this place. > > This one place is now defined by DefaultDocument. > The implementation is not nice, I agree. > > > > That only makes sense when we introduce UUIDs since > > otherwise we will run again in the egg chicken problem of meta data, > > file and mapper. > > This problem is solved. But what remains is the problem that meta data > sources have to be moved when document locations change. >
well see the other thread, it is not really solved. ;) > > > How can we implement it? > > I'd start with adding UUIDs to the sitetree and use them for content lookup. > In a first step we could use the document IDs, because that wouldn't > require too many changes to the code. > > -- Andreas Thanks for your support. :) salu2 -- Thorsten Scherler COO Spain Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
