David Casal wrote:
6. The new block contain some new and intersting stuff that is not
available before. After a number of refactorings it consists of a
number of blocks that are reusable and solves well defined concerns.
Now the user puts the blocks in a new project in Sourceforge (or
cocoondev.org etc).
That's a v cool thought. Do you envision that at this point, a user who
finds the reusable blocks in the Sourceforge project, could download
them and run them as they are?
yes
Meaning, would they contain Cocoon's
core, or as you explain further, would it only contain the parts of the
Cocoon core it needs?
It doesn't contain any parts of Cocoon core at all. It only has to compile
against Cocoon core's interfaces.
Might it instead contain only the meta info needed
to downloaded needed core and non-core components during install?
Are you guys thinking of a central Cocoon OSGi repository all these
externally developed block-built apps would rely on?
yes, see http://wiki.apache.org/cocoon/BlockImplementation (block deployer)
--
Reinhard P�tz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
