One could use an immediate extension (application file)
<!ELEMENT extension (meta | configure)* >
<!ATTLIST extension
name CDATA #REQUIRED
class CDATA #REQUIRED
immediate %attribute-flag; "no"
>
Still in Tap4 !
Geoff
On 12/10/05, Kent Tong <[EMAIL PROTECTED]> wrote:
> Bryan Lewis <bryan <at> maine.rr.com> writes:
>
> > In our old Engine we preloaded all the pages at the first request, to
> > check that there were no errors and to avoid delays later. We hooked
> > into the startup sequence by overriding createVisit(). That method's
> > gone now, and so are others like createGlobal() and setupForRequest().
> > I tried a couple of probably-silly approaches -- hooking
> > requestInitialized() and even service() -- but I can't see a way to
> > do this in a place where I can get both a requestCycle and the
> > servletContext.
>
> If the first request is always for the page service, you may extend
> the PageService class and override its service() method. In the
> serivce() method you can get access to the request cycle and the
> servlet context (through injection). Then make a contribution
> to the tapestry.services.ApplicationServices configuration point.
>
> --
> 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]
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
