1 |
torben |
772 |
/* using java.util.timer is the most simple but also very inflexible - and It is considered less-than-nice in relation to the app server since |
2 |
|
|
* it executes the scheduled task in a new background thread that the appserver has no control over. |
3 |
|
|
* |
4 |
|
|
*/ |
5 |
|
|
|
6 |
|
|
package dk.thoerup.schedulesamples; |
7 |
|
|
|
8 |
|
|
import java.io.IOException; |
9 |
|
|
import javax.servlet.ServletException; |
10 |
|
|
import javax.servlet.http.HttpServlet; |
11 |
|
|
import javax.servlet.http.HttpServletRequest; |
12 |
|
|
import javax.servlet.http.HttpServletResponse; |
13 |
|
|
|
14 |
|
|
/** |
15 |
|
|
* Servlet implementation class JavaTimer |
16 |
|
|
*/ |
17 |
|
|
public class JavaTimer extends HttpServlet { |
18 |
|
|
private static final long serialVersionUID = 1L; |
19 |
|
|
|
20 |
|
|
|
21 |
|
|
|
22 |
|
|
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { |
23 |
|
|
} |
24 |
|
|
|
25 |
|
|
} |