Carsten Ziegeler wrote:
Sylvain Wallez wrote:
And that is probably the main reason why the Fortress effort 'stalled' ; Cocoon is so
much more than dependency+conf injection.
Let me strongly disagree on this point. The Fortress effort
stalled because the sitemap engine (aka treeprocessor) was
intimately tied to some of the features of the ECM. The
design choices of the container had slipped through into the
component code. I am the culprit on this point.
There was some refactoring of the treeprocessor lately that
removes that dependency on ECM internals. It's still tied to
Avalon framework concepts though, although it could be fairly
simple to cut that dependency.
The former cvs for 2.2 contains a version that runs on Fortress
(without using meta-information).It's not difficult to add
this to our current 2.2 version in SVN, but currently I don't
see a real need for it. For 2.1.x ECM works fine, and with
"Real blocks" we will have a different core anyway.
Yup. Agree.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
