It is very important that the abstract base class be in a controlled Tapestry folder; typically you'll put the base class in root.base (and your concrete pages go in root.pages).
If Tapestry doesn't get a chance to transform the class, then annotations and the rest simply don't happen. This is in the documentation, it will be clearer in the tutorial (still in progress). On 6/28/07, Dan Adams <[EMAIL PROTECTED]> wrote:
I put a mixin in an abstract parent class of a component and it was ignored. I just moved it down to the concrete class and it worked fine. Is this the decided behavior? -- Dan Adams Senior Software Engineer Interactive Factory 617.235.5857 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
