I don't think this can be done in 4 (because of the abstract approach + dynamic subclasses), but i believe it's planned for 5.
See http://wiki.apache.org/jakarta-tapestry/Tapestry5Roadmap : * Annotations based. JDK 1.5. * No XML for pages and components. Just HTML and Annotations. * Concrete, not abstract, page and component classes * No inheritance imposition Norbert Sándor (JIRA) wrote: > [ > http://issues.apache.org/jira/browse/TAPESTRY-907?page=comments#action_12374913 > ] > >Norbert Sándor commented on TAPESTRY-907: >----------------------------------------- > >Thanks for the fast response! I'll use your tip. > >But the adventage of using annotations (besides others) is that more complex >component inheritance usecases are possible than without using annotations. >Therefore in this case the framework should check if a concrete implementation >is available in the subclass. > >Regards, >Norbi > > > >>overridden parameter problem >>---------------------------- >> >> Key: TAPESTRY-907 >> URL: http://issues.apache.org/jira/browse/TAPESTRY-907 >> Project: Tapestry >> Type: Bug >> >> > > > >> Components: Annotations >> Versions: 4.0.1 >> Reporter: Norbert Sándor >> Attachments: test.zip >> >>The output of the attached simple test is "false false". >>I expected "false true". >>What do you think? >>Regards, >>Norbi >> >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
