Thorsten Scherler wrote:
On Fri, 2005-08-12 at 14:39 +0200, Felix Röthenbacher wrote:
...
My opinion is, that the jcr block is not of much use for a CMS as it
uses a filesystem model rather than a CMS data model.
The implementation of access to repository data as a Source is certainly
indicated.
Hmm, wouldn't make it more sense to enhance the JCR Block to fit *as
well* the need of a cms? I mean most of us lenya committer has write
access to cocoon.
Your suggestion are very interesting but I would like to see that going
back to cocoon. We would not loose the over-side and still have a JCR
block that is able to focus more on the cms usecase.
WDYT?
I agree with you that it is generally preferable to use an existing
Cocoon component. The problem here is that the way you access a
repository is heavily dependent on the repository data model (in the
case of the jcr block it is a filesystem model). Adapting the jcr block
to the needs of Lenya's data model will not be of much use for other
CMS's / applications based on Cocoon.
It's the same with data models for database applications: there will
be no general model for all applications, so you design the model
according to your needs, with the consequence that you also have
to adjust your accessors (say: protocols) to the given model.
The jcr block may be changed in a way to use it as a general
accessor of the repository, dropping the filesystem functionality.
- Felix
salu2
--
Felix Röthenbacher [EMAIL PROTECTED]
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
