I think that, in any case, Tapestry could return a list of the pages
that are currently pooled, since it appears to use some clever file
and reflection routines to call not-instanced pages. I've created new
classes in the middle of a session and seen TP call them without
needing a restart.

On 9/2/05, Patrick Casey <[EMAIL PROTECTED]> wrote:
> 
> 
>             Is there a way to get a list of all the pages in the current
> application? Preferably one that can be accessed statically so I can get the
> list outside of the response cycle?
> 
> 
> 
>             --- Pat
> 
> 
> 


-- 
I have enough money to last me the rest of my life, unless I buy something.
    Jackie Mason

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to