Michael Wechner wrote:
Andreas Hartmann wrote:
My suggestion is to integrate it within the blog publication first
and then expand from there.
I disagree to the "per publication" approach.
the reason I am suggesting this is to help build trust into JCR
and that it won't destabilize the core
I agree, therefore I suggested the polymorphic approach.
It should look like this:
+-------------+ +----------+
| default pub | | your pub |
+-------------+ +----------+
| |
v v
+-----------------------------+
| Lenya repository API |
+-----------------------------+
| |
v v
+-------------+ +----------+
| source repo | | JCR repo |
+-------------+ +----------+
instead of
+-------------+ +----------+
| default pub | | your pub |
+-------------+ +----------+
| |
v |
+----------------+ |
| Lenya repo API | |
+----------------+ |
| |
v v
+-------------+ +----------+
| source repo | | JCR repo |
+-------------+ +----------+
Advantages:
- improvement of the Lenya repo API
- no need to replicate functionality in your publication
- ability to switch between repo implementations
At some point in the future, it will probably make sense to
drop the source repo, because this allows us to leverage
the full power of JCR (which can't be replicated with
sources with reasonable efforts). But until then, I'd like
to do a smooth transition by using the common Lenya repo layer.
Storing resources should be a service which is provided by the Lenya
core.
There should be exactly *1* way to do it.
I don't think so, but that's another topic
I'd prefer to use a polymorphic approach, which means we can
switch between the JCR-based and Source-based Lenya repository.
fine with me, but does such an interface within 1.4-dev already exist?
http://wiki.apache.org/lenya/OverviewRepository
The entry point is the RepositorySource, which uses a Node to
store data. Of course it's not very powerful, but it allows to
use another repo implementation by providing another NodeFactory.
This is not yet configurable (no need for this by now), but
that can be accomplished in a minute.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
