ComponentSource can almost do what you want. I think I'll add a few more methods to make it easier to obtain a page given a logical page name or a page class.
On 12/9/06, Kent Tong <[EMAIL PROTECTED]> wrote:
Hi, In an attempt to catch up with T5 and maybe to make some small contributions, I'm trying to port the Workbench to T5. In the process I found that it seems impossible for a component to get a page by name that is provided at runtime (eg, in the case of a Tab component that knows about the names of the tab pages at runtime only). @InjectPage requires a constant page name. I'm thinking about making the RequestPageCache available through the infrastructure service. Do you think this is the way to do it? -- Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- 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
