Andreas Hartmann wrote:
yesterday I noticed that it's possible to build external blocks
with Cocoon since 2.1.7. That would enable us to use the Cocoon
block concept for modularization, without building our own infrastructure.
Maybe it is even possible to implement plug-ins / publets as blocks?
More info:
http://wiki.apache.org/cocoon/Blocks
note that for this to make much sense, we should move to cocoon 2.2,
where the real blocks will happen. the stuff in 2.1.7 is merely a
stopgap towards that.
http://www.planetcocoon.com/node/2062
note that the current thinking seems to be to move to OSGI, the same
kernel that eclipse uses. this would mean that cocoon blocks would
basically look like eclipse plugins.
Anyway, IMO the codebase would benefit from a better modularization,
we have too many inter-component dependencies at the moment. A
separation into blocks would certainly lower the entry barrier
as well.
definitely true, and i remember us attempting to make wf into a cocoon
block before
I imagine something like
+------------------------------------------------------- ... --+
| Usecases |
+------------+-------+-----------+----------+-------+--- ... --+
| Repository | Lenya | Site | Workflow | BXE |
| Block | Core | Structure | Block | Block | ...
| | Block | Block | | |
| | | | | |
+------------+-------+-----------+----------+-------+
I have no idea about the impact on the codebase yet, but I'd like
to do some investigation. My idea is not to do a major refactoring,
but merely to create self-contained modules wherever this is possible.
agreed on the approach. refactoring for the sake of refactoring doesn't
buy us anything at this time. and the current cocoon block build system
is rather complicated and brittle. i wouldn't want to switch to that
until after the dust settles over at cocoon, and they have figured out
whether to use maven etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
