|
50 | 50 | /** |
51 | 51 | * Build and create a {@link Scheduler Quartz Scheduler} and {@link Job jobs}. |
52 | 52 | * |
53 | | - * <h1>Getting Started</h1> |
| 53 | + * <h1>usage</h1> |
54 | 54 | * |
55 | 55 | * <pre> |
56 | 56 | * { |
|
60 | 60 | * |
61 | 61 | * Previous example will startup Quartz and schedule MyJob. |
62 | 62 | * |
63 | | - * <h1>Jobs</h1> |
| 63 | + * <h1>jobs</h1> |
64 | 64 | * <p> |
65 | 65 | * A job can implement the {@link Job} interface as described in the <a |
66 | 66 | * href="http://quartz-scheduler.org/documentation">Quartz documentation</a> |
|
75 | 75 | * package name of the job class. |
76 | 76 | * </p> |
77 | 77 | * |
78 | | - * <h2>Job methods</h2> |
| 78 | + * <h2>job methods</h2> |
79 | 79 | * <p> |
80 | 80 | * A job method must follow this rules: |
81 | 81 | * </p> |
|
89 | 89 | * |
90 | 90 | * The next section will you show how to add a trigger to a job and some examples too. |
91 | 91 | * |
92 | | - * <h1>Triggers</h1> |
| 92 | + * <h1>triggers</h1> |
93 | 93 | * <p> |
94 | | - * Trigger are defined by the {@link Scheduled} annotation. The annotation defined a single and |
| 94 | + * Trigger are defined by the {@link Scheduled} annotation. The annotation defines a single and |
95 | 95 | * required attributes, which is basically a trigger expression or a reference to it. |
96 | 96 | * </p> |
97 | 97 | * |
|
143 | 143 | * expressions. |
144 | 144 | * </p> |
145 | 145 | * |
146 | | - * <h1>Grouping jobs together</h1> |
| 146 | + * <h1>grouping jobs together</h1> |
147 | 147 | * <p> |
148 | 148 | * If you have two or more jobs doing something similar, it is possible to group all them into one |
149 | 149 | * single class: |
|
163 | 163 | * } |
164 | 164 | * </pre> |
165 | 165 | * |
166 | | - * <h1>Dependency Injection</h1> |
| 166 | + * <h1>dependency injection</h1> |
167 | 167 | * <p> |
168 | 168 | * Not much to add here, just let you know jobs are created by Guice. |
169 | 169 | * </p> |
|
201 | 201 | * } |
202 | 202 | * </pre> |
203 | 203 | * |
204 | | - * <h1>Configuration</h1> |
| 204 | + * <h1>configuration</h1> |
205 | 205 | * <p> |
206 | 206 | * Example: Setting max number of threads |
207 | 207 | * </p> |
|
216 | 216 | * <code>*.conf</code> file, NOT in a custom <code>quartz.properties</code> file. |
217 | 217 | * </p> |
218 | 218 | * |
219 | | - * <h2>Jdbc Store</h2> |
| 219 | + * <h2>jdbc store</h2> |
220 | 220 | * <p> |
221 | 221 | * Jdbc Store is fully supported but it depends on the <code>jooby-jdbc</code> module. So, in order |
222 | 222 | * to use the Jdbc Store you need to follow these steps: |
|
243 | 243 | * org.quartz.jobStore.dataSource = db |
244 | 244 | * </pre> |
245 | 245 | * |
246 | | - * <h1>Adding jobs programmatically</h1> When {@link Scheduled} isn't not enough and/or if you |
247 | | - * prefer to build jobs manually, you can try |
| 246 | + * <h1>adding jobs programmatically</h1> |
| 247 | + * <p> |
| 248 | + * When {@link Scheduled} isn't not enough and/or if you prefer to build jobs manually, you can try |
248 | 249 | * one of the available alternatives. |
| 250 | + * </p> |
249 | 251 | * |
250 | 252 | * <p> |
251 | 253 | * Example 1: build the trigger and use default job naming |
|
0 commit comments