Single inheritance should not be a problem if your design is good, which means that your components' taxonomy must be consistent. On the other hand having more component classes brings developers a stronger abstraction and a more readable code.
I'm -1 on adding more subclasses to Wicket's type hierarchy.

We have single inheritance in Java, why waste it for something which could 
equally well be implemented with behaviors?

Sven


Am 30.11.2010 um 13:18 schrieb Andrea Del Bene:


Reply via email to