Andreas Hartmann wrote:
Michael Wechner wrote:
Andreas Hartmann wrote:
Hi Lenya devs,
actually this is an obvious problem, but I was confronted with
the issue when I wrote the migration target to remove the source
extensions.
The DocumentIdToPathMapper interface allows custom content structures,
which makes it impossible to provide generic automated migration tools
when the internal storage changes.
If someone needs a custom data structure, it must be very clear that
the no automated migration will be provided.
if one has a custom data structure (and I am not refering to the meta
files, but the actual data)
and Lenya provides the right API, then one doesn't have to migrate
the content.
That's true, but the DocumentIdToPathMapper is just an indirection
between the content object model and the storage layer. It determines
how documents are mapped to nodes. IMO it is sufficient if the node
factory maps the nodes to files (or JCR nodes or whatever).
I don't fully understand how this relates to the above. Can you give an
example?
Michi
-- Andreas
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
+41 44 272 91 61
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
