You can also consider registeing tapestry ApplicationInitializer
See hivemodule of the tapestry.init
http://tapestry.apache.org/tapestry4/tapestry/hivedocs/config/tapestry.init.ApplicationInitializers.html
http://tapestry.apache.org/tapestry4/tapestry/hivedocs/module/tapestry.init.html
On 21/
I think the EagerLoad service point is meant for this kind of stuff:
http://hivemind.apache.org/hivemind1/hivedocs/service/hivemind.EagerLoad.html
On Wed, 21 Feb 2007 00:09:24 +0100, Gurps <[EMAIL PROTECTED]> wrote:
ok, what if I have a daemon class that polls something in the database
every
ok, what if I have a daemon class that polls something in the database every
now and then. However, on tapestry startup it must be already initialized.
Would i use a runnable class and then just use hivemind.Startup? Is this the
best practise?
Thanks
Howard Lewis Ship wrote:
>
> An "ASO" that
