I think that's all just the classloader at work :). Howard may have
done some double-secret coolness, but the ability to load a class on the fly
(even a class which didn't exist at JVM start) is a standard classloader
behavior (I've got a library somewhere or other that generates beans on the
fly and compiles them).
What I'm trying to do here doesn't strike me as all that unusual. I
want each user to be able to choose their own home page. So I want to give
them a (somewhat filtered) list of pages in a drop down. I'd like to pluck
the list out of Tapestry (it's all defined in the .application file, so I
know its rattling around in memory somewhere or other).
--- Pat
> -----Original Message-----
> From: Darío Vasconcelos [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 02, 2005 11:06 PM
> To: Tapestry users
> Subject: Re: Get a list of pages in current application?
>
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
