cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Re: [RT] Block usage
Date Fri, 27 May 2005 11:09:54 GMT
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 
>> 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? 


> 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 (block deployer)

Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}


View raw message