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.
Michi
IMO this should require
more than implementing an innocent looking interface. The storage
facility should be a separate component, and the documentation has
to reflect that you're on your own re. the content when you use a
custom implementation.
WDYT?
-- 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]
