[EMAIL PROTECTED] wrote:
On 9/16/05, Ross Gardler <[EMAIL PROTECTED]> wrote:
Thorsten Scherler wrote:
On Fri, 2005-09-16 at 16:21 +0200, J. Wolfgang Kaltz wrote:
"One key feature of Lenya (...) is that all content is stored in XML
files. (...) Another advantage of this approach is that all content is
human and machine readable, so there is no possibility of being tied to
a closed binary format: Lenya data should be free data forever."
Moving to storing information in Jackrabbit means a binary format; not a
closed one of course, but still ... is this a concern ? (Or is it just
me ;) )
That is a valid point you have there.
Maybe we really should implement a repository layer between the rep. All
components should request this layer.
If it means I can swap in a different repo by providing a jar and a
new config file this would be great.
Will all repository interfaces include readAll() and writeAll()
functions using a standard format? Then converters can be written:
newRepository.writeAll(oldRepository.readAll());
We would have to provide this functionality, though I think it will
be available from somewhere anyway. All it needs is a traversal over
the repo tree.
Add a "Create Archive" task to read the current repository and create
the "human and machine readable XML" repository in a specified
directory.
Felix Roethenbacher already implemented a usecase to export a
publication or the whole Lenya repository as XML.
The easier alternative is every new repository imports from and
exports to the old standard XML repository format. Then converting
from Jackrabbit to MyNewRepository means exporting, then importing the
results to the new repository. The "Create Archive" function would
just run the export for the current repository.
That would certainly be an option. We need the import anyway to support
migration from 1.2.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
