cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <>
Subject Re: Java components in blocks
Date Thu, 14 Apr 2005 15:33:11 GMT
Stefano Mazzocchi wrote:

> Pier Fumagalli wrote:
>>> IMO, we should start simple and add functionality when needed. 
>>> Remove things is much harder. Also even if we chose to go for 
>>> alternative 4. an important message from Pier that we should take 
>>> into account is that component exposure adds complexity. So if we go 
>>> that way, we should have mechanisms that so that we can have 
>>> detailed control over what components and classes a block exposes. A 
>>> block that exposes much will be much more likely to create conflicts 
>>> with other blocks.
>> Glad that we have agreement on this! :-D
> Ok, you changed my mind. Let's keep the concerns separate and see what 
> happens.

Frankly, I'd love to see how this will even work.  If someone could 
explain how the cron block can be a block without exposing components 
then maybe I could understand.  I really want to understand how this 
could apply to the portal block, but the cron block is a lot simpler.


View raw message