El vie, 10-03-2006 a las 15:16 +0100, Andreas Hartmann escribió: > Thorsten Scherler wrote: > > [...] > > >>> 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. ;) > > Yes, unfortunately it can't be solved with the current architecture. > > The problem is: > > - a repository node stores its meta data > - the meta data source URI is derived from the node source URI > - the node source URI depends on the meta data (source extension) > > I don't see a solution that doesn't require migrating the content. > > IMO the cleanest solution would be a flat structure based on UUIDS. > > /content/12345 -> document > /content/12345.meta -> meta data
+1 I as well believe it is the only solution, since we are running again and again into this cycle. Let us do this ASAP, then we have time to test it before a release. BTW this steps helps to migrate to jcr easier, right? salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
