[...]
>>> 1) add a filesystem-based implementation if you don't want to rely on JCR
>>>
>>
>> I think we should do that, because we don't know how JCR will behave in the
>> first
>> place for productive environments and with the FS we know exactly where the
>> problems
>> are and how we can fix them.
>>
>
> +1
> In our daily lenya business it may happen that we have to fix
> things up in the FS. Therefore having a FS based system too, seems
> important to me.
> As an alternative there should be tools to export and import Documents
> out-of/into the repository outside of the cms like
>
> export documet to FS --> Fix error --> import into repo
I see the point, we're not living in a perfect world ...
But that should be possible using a generic JCR browser
or editing tool. IMO this argument is not sufficient for
providing a filesystem-based implementation (which requires
maintenance).
We once agreed on a JCR-only approach. I don't want to start
the discussion again, I just wanted to point out the option
of implementing a file-system based repository (I'm sure that
would have been the next question). The (in)famous phrase
"feel free to implement this" applies, but IMO we should focus
on the JCR-based implementation to end up with a stable and
performant product after a reasonable timespan.
-- Andreas
--------------------------------------------------------------
Andreas Hartmann [EMAIL PROTECTED] +41 1 272 9161
Wyona AG, Hardstrasse 219, CH-8005 Zurich
Open Source CMS http://www.wyona.org http://www.wyona.com
--------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
