Hi Chris, your solution looks nice. I saw your patch attached to the JIRA issue, actually you proposed to add a method to the ComponentClassResolver on 5.0.7, but i can't figure out how I can do this on 5.0.6... how are you doing it?
2007/11/20, Chris Lewis <[EMAIL PROTECTED]>: > > I've created a JIRA and included a patch: > https://issues.apache.org/jira/browse/TAPESTRY-1923. I actually had use > for this as well - I'm working on a T5 component lib that includes a > demo app for showcasing the components. I wanted to simply enumerate all > known pages (excluding Start) and create links to them in the start > page. The idea would be that all pages (or perhaps those only in a > certain package) will display a component, so autonomously creating > links to them would prevent me from having to maintain the demo app as > components are added. > > Howard Lewis Ship wrote: > > Sure add an issue. > > > > ... and a patch :-) > > > > Just curious: why do you need to list of all pages? > > > > On Nov 19, 2007 1:14 PM, Marcus <[EMAIL PROTECTED]> wrote: > > > >> Hi Howard, > >> > >> I agree with you, maybe if ComponentClassResolver can have a method > >> where we can get page names, just when we want? > >> > >> > >> Thanks, > >> > >> Marcus > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > > > > > > > -- Atenciosamente, Marcelo Lotif
