I think the Cocoon project has such a facility. I'm not sure how
complicated it would be to pull out that functionality, but their work
might be worth looking at for this.
--David
Parsons Technical Services wrote:
With all the questions and suggestions flying around, a question to
the other programmers: If one was to write a class for the purpose of
running classes at set times, what pitfalls would one need to watch for?
I have a class that loads on startup and runs a continuous loop that
is timed (sleeps, wakes up, does something, sleeps again). It runs
fine, but I know that it could be better.
Any guidance or suggestions would be appreciated. And maybe we could
create an add-on and post it for use in apps that need such a device.
Thanks
Doug
----- Original Message ----- From: "Nikola Milutinovic"
<[EMAIL PROTECTED]>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Sent: Thursday, March 03, 2005 6:55 AM
Subject: Re: Equivalent of Resin "run-at" servlet configuration
Subramanya Sastry wrote:
Hello,
I am developing a Java web application, and one of the requirements
is to run a particular servlet periodically, or even at specified
times. Resin provides this ability via its "run-at" configuration
element for servlets in web.xml
Example Resin configuration:
<servlet>
<servlet-name>download</servlet-name>
<servlet-class>DownloadNewsServlet</servlet-class>
<run-at period='360m'/>
</servlet>
However, I haven't found an equivalent configuration for Tomcat. I
searched
the web and was unsuccessful. So, any pointers as to how I could
achieve this
for Tomcat would be appreciated.
There is none and shouldn't be any. I understand the need to run
periodical tasks, but J2EE specification, prior to 1.4 has no such
provisions. Further, Servlet/JSP specification has no such provision,
even in J2EE 1.4. You'd be best advised to setup a cron-job to
perform this periodic activity. There are several good HTTP client
packages out there, Jakarta-Commons HTTPclient, to name one, that
will help you in building the client side of your cron-job.
Nix.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
