Michael Wechner wrote:
Andreas Hartmann wrote:
why do you consider JCR as publet. I would say that should be part of
the core.
-1
Lenya still suffers from too many cross-component dependencies.
> which one do you mean?
- some components access the revision controller directly, which should
be a concern of the repository service
- the transaction classes are used by various other classes
(this is still work in progress, I'm doing a small re-design)
- XML handling is done by various components
- the publication API depends on the workflow component and the
other way round, whereas this dependence has been reduced to a
minimum in 1.4
There should be no dependencies from the core to the JCR-related
classes, only the other way round.
depends if one considers JCR as core functionality
I stated my opinion on this subject quite frequently.
At the moment, I'd strongly discourage spreading JCR references
across the codebase and hard-wiring the JCR integration. This would
only make things more complex and would not do any good.
The question is not if it is core functionality. IMO it is great
to support JCR out of the box. But modularization is a very important
design principle which we cannot neglect. Publets allow to separate
functionality into distinct modules.
The JCR publet offers just another
implementation of the Lenya repository components.
ok, but I think it's very confusing, because I don't
think JCR is a publet neither, or what does publet mean
to you? Maybe we should clarify this first ;-)
IMO a publet is a module which provide a certain functionality.
This can be for instance a set of resources or a certain
implementation of a service.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
