DocumentIdToPathMapper in API breaks backwards compatibility

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. 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


-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache
Lenya
http://www.wyona.com     
                http://lenya.apache.org
andreas.hartmannwyona.com                     andreasapache.org


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org