avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mircea Toma" <mirceat...@apache.org>
Subject Re: [VOTE] avalon's future - take 2 (was [vote] avalon's future )
Date Tue, 26 Nov 2002 23:59:07 GMT
> Stepanossov, Kirill wrote:
> > Committers, if this accepted, could you still leave different "toolkits"
for
> > building customized containers available ?
>
> Why does everybody here think that COP and inheritance don't mix?

They can mix but not very elegantly. COP is promoting Composition as the
main design pattern isn't it?

> Who
> said that?
>
> Example: Cocoon will need the embeddable container to implement cocoon
> blocks, but cocoon blocks will have features that are cocoon-specific,
> so Cocoon will have to "extend" this container to fit its needs.

If you think about blocks in the same way Cocoon extends ECM to provide the
specific functionality then you have a clear case were inheritance is not
doing a very good job.....

Mircea


--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message