This has come up a few times; please check the mailing list history. Subclasses are the proper way to go, and I'm strongly opposed to sharing templates in any other fashion.
On 7/7/07, Shing Hing Man <[EMAIL PROTECTED]> wrote:
In Tap 4, two different Tapestry pages can share the same java page class, foo.java say, by setting the page-specification attribute class="foo.java". How can this be done in Tap 5 ? A workaround would be to have a subclass of foo.java for each Tapestry page. But then I will have many subclasses of foo.java if there are many pages sharing foo.java. Thanks in advance for any assistance! Shing Home page : http://uk.geocities.com/matmsh/ ___________________________________________________________ Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your free account today http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.html --------------------------------------------------------------------- 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]
