Hola Pablo,
as already stated Tapestry should be used with a collaboration
development strategy instead of inheritance.
When you inherit a component, you're only inheriting his
javaclass-defined properties.
Since much of the descriptive behaviour of the component is in the jwc
descriptor you don
In general, Tapestry is designed to be used with collaboration instead of
inheritance. When we first started using Tapestry about a year ago we had
the same stumbling block. We overcame it by rethinking our component
strategy into small collaborative components that do not use inheritance of
compon
