J. Wolfgang Kaltz wrote:
[...]
To be honest, I'm not sure I understand ;)
I am wondering about one thing though: is it our goal to
1. replace Lenya's content sources by JCR (be it through Cocoon or not),
meaning all content *must* be stored in a JCR-compliant backend;
or
2. add JCR as one possible backend, while content need not necessarily
reside in a JCR-repository, but could also be in files (as is the case
now), in a database, ...
IMO number (2) is the way to go, at least for the next steps.
IIUC having the usecases directly using the Cocoon repository block
would imply option 1 ?
No, it would mean that we would have to provide an implementation of
the repository block interfaces for our existing "storage system"
(files, revision controller, meta data).
Whereas keeping "Lenya repository interfaces" would allow for 2. as well.
Would the following make sense ?
+-----------------------------------------------------+
| Lenya usecases etc. |
+-----------------------------------------------------+
| Lenya repository interfaces |
+-------------------------+-+-----------------+-------+
| Cocoon repository block | | Lenya repo (file) impl | ...
+-------------------------+ +-------------------------+
That would be an option as well.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
