Andreas Hartmann wrote:
Hi Lenya devs,
after countless workarounds and lots of outbursts of fury I have now
changed the persistence layer so that documents are stored without
extension:
foo/index
foo/index.meta
instead of
foo/index.xml
I think this should be decided by the resource itself
foo/index.xml.meta
There's a simple migration target in migration-build.xml:
./build.sh migrate-extensions -Dpublication=default
but it works only for .xml extensions and it doesn't work for
"outsourced" content.
I think it doesn't make sense to generalize this target, it is
more efficient if you modify the target to fit your needs:
<target name="migrate-extensions">
<property name="publication" value=""/>
<move todir="${build.webapp}/lenya/pubs">
<fileset dir="${build.webapp}/lenya/pubs/${publication}">
<include name="content/**"/>
<exclude name="content/*/site.xml"/>
<exclude name="content/*/sitetree.xml"/>
</fileset>
<compositemapper>
<mapper type="glob" from="*.xml" to="*"/>
<mapper type="glob" from="*.xml.meta" to="*.meta"/>
</compositemapper>
</move>
</target>
Please complain if problems occur (this will basically happen if
there still are pieces of code which bypass the repository layer).
Sorry for the inconvenience,
well, can't we discuss these things before we just go ahead?!
It's not about inconvenience but rather about *ignoring* other people's
opinion completely ...
I think it's very wrong that Lenya forces people to adapt a certain path
structure and the reason I think this is completely wrong is because
Lenya is not the only application on this planet handling data. Various
applications should be able to share data and this means the
applications need to be customizable and not the data.
In the case of Lenya this doesn't seem to be the case anymore or do I
completely misunderstand something?
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]
