cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hunsberger, Peter" <Peter.Hunsber...@stjude.org>
Subject RE: defaulting to a matcher when another one is not present
Date Wed, 09 Oct 2002 16:39:04 GMT
>> If you think that point 2) is valid, let me ask you; do you ever use
>> inheritance in Java?  Do you ever use inheritance where you only want to
>> override part of the behavior of the super class but otherwise let the
rest
>> of the processing continue on as normal?
>
> Usually I never do this, I use composition, not inheritance.
>
> I have never found the need to inherit from a non-abstract class yet, so 
> you can understand why I don't see the need.
> Invert the selection logic, put it in the parent, not the child.

Umm, forgot to comment on this: if I invoke another classes methods I'm
certainly free to deal with any exception as I see fit? It seems to me that
a sitemap doesn't implement the equivalent of composition either...


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message