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 component properties.
Richard -----Original Message----- From: Pablo Ruggia [mailto:[EMAIL PROTECTED] Sent: Thursday, April 21, 2005 6:49 AM To: Tapestry users Subject: Specification Inheritance Hi !! I'm new to Tapestry and I've found a limitation that I don't like very much. When I extend a Component, I can't inherit it's "supercomponent" specification. I have to copy-paste, all properties, beans and assets i want to have from superclass. Am I correct, or there is some way to achieve it without copy-paste. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
