i didn't think tapestry had that kinda control, so we use quartz scheduler,
which is invoked by the servlet during loading of the application. the
application can use the quartz methods to set up new jobs to be chron'd or
one time runs. Its works really well. we use it to import and export data
into our DB and compile stats on our database. quartz is pretty easy to
setup and manage.
depending on your context it might be more efficent to use another box to
handle this job, depending on the complexity of the status check. what is it
that you want it to do?
evan.
----- Original Message -----
From: "craigham" <[EMAIL PROTECTED]>
To: <users@tapestry.apache.org>
Sent: Wednesday, June 27, 2007 10:39 PM
Subject: Re: upgrade to 4.1.1
I tried this to no avail, am I getting close?
I realize this doesn't address the timer, but as a first step i was
trying
to call a method on the load of the screen.
@EventListener(elements = "body", events = "onload")
public void doCheck() {
logger.debug("Do check called");
}
--
View this message in context:
http://www.nabble.com/upgrade-to-4.1.1-tf3983447.html#a11336081
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
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]
