Andreas Hartmann wrote:
simon litwan wrote:
hi list
i'm working on a customers request about losing jobs after paste/rename
url. they wish the scheduled jobs should move with document. but they
also would be satisfied with a warning on the paste/rename screen that
the jobs will get lost.
[...]
That's a good example for a problem caused by mixing concerns -
document storage and site structure. If they were separated, the
problem would not occur. I suggest that we reconsider storing documents
in a non-structured way and implement site structures as views on the
document repository.
I think you can still store the documents in a structured way, but each
document
has a unique ID which is mapped onto the path within the
hierarchy/structure, e.g. by
hashmap. This unique ID (uid) is then being used within the Scheduler or
for references
for instance and not the path itself.
We have built this for a customer of ours and it seems to work pretty well.
I hope that we can contribute the lessons we learned in the near future.
Btw, it seems to me that Jackrabbit is doing pretty much the same thing,
whereas
Jackrabbit is managing this "hashmap", whereas I am not sure if I might
have misunderstood something. For instance I am not sure if one can
access/use the unique
IDs from Jackrabbit and use them within the application. On the other
hand AFAIK
the persistence manager only receices the UIDs.
Anyway, I am pretty conviced that we will be able to solve this problem
within Lenya in the very near future.
Michi
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - 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]
