Author: buildbot
Date: Fri Dec 13 16:46:30 2013
New Revision: 890242
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Dec 13 16:46:30 2013
@@ -1 +1 @@
-1550337
+1550766
Modified:
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
Fri Dec 13 16:46:30 2013
@@ -160,15 +160,48 @@
<p>For managing queues, the Sling Job Handler uses the OSGi ConfigAdmin - it
is possible to configure one or more queue configurations through the
ConfigAdmin. One way of creating and configuring such configurations is the
Apache Felix WebConsole.</p>
<h4 id="queue-configurations">Queue Configurations</h4>
<p>A queue configuration can have the following properties:</p>
-<p>| <em>Property Name</em> | <em>Description</em> |
-| <em>queue.name</em> | The name of the queue. If matching is used for
topics, the value {0} can be used for replacing the matched part. |
-| <em>queue.type</em> | The type of the queue: ORDERED, UNORDERED,
TOPIC<em>ROUND</em>ROBIN, IGNORE, DROP |
-| <em>queue.topics</em> | A list of topics processed by this queue.
Either the concrete topic is specified or the topic string ends with /<em> or
/. If a star is at the end all topics and sub topics match, with a dot only
direct sub topics match. |
-| </em>queue.maxparallel<em> | How many jobs can be processed in
parallel? -1 for number of processors.|
-| </em>queue.retries<em> | How often should the job be retried. -1 for
endless retries. |
-| </em>queue.retrydelay<em> | The waiting time in milliseconds between
job retries. |
-| </em>queue.priority<em> | The thread priority: NORM, MIN, or MAX |
-| </em>service.ranking* | A ranking for this configuration.|</p>
+<table>
+<thead>
+<tr>
+<th><em>Property Name</em></th>
+<th><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><em>queue.name</em></td>
+<td>The name of the queue. If matching is used for topics, the value {0} can
be used for replacing the matched part.</td>
+</tr>
+<tr>
+<td><em>queue.type</em></td>
+<td>The type of the queue: ORDERED, UNORDERED, TOPIC, ROUND-ROBIN, IGNORE,
DROP</td>
+</tr>
+<tr>
+<td><em>queue.topics</em></td>
+<td>A list of topics processed by this queue. Either the concrete topic is
specified or the topic string ends with /* or /. If a star is at the end all
topics and sub topics match, with a dot only direct sub topics match.</td>
+</tr>
+<tr>
+<td><em>queue.maxparallel</em></td>
+<td>How many jobs can be processed in parallel? -1 for number of
processors.</td>
+</tr>
+<tr>
+<td><em>queue.retries</em></td>
+<td>How often should the job be retried. -1 for endless retries.</td>
+</tr>
+<tr>
+<td><em>queue.retrydelay</em></td>
+<td>The waiting time in milliseconds between job retries.</td>
+</tr>
+<tr>
+<td><em>queue.priority</em></td>
+<td>The thread priority: NORM, MIN, or MAX</td>
+</tr>
+<tr>
+<td><em>service.ranking</em></td>
+<td>A ranking for this configuration.</td>
+</tr>
+</tbody>
+</table>
<p>The configurations are processed in order of their service ranking. The
first matching queue configuration is used for the job.</p>
<h4 id="ordered-queues">Ordered Queues</h4>
<p>An ordered queue processes one job after the other.</p>
@@ -207,7 +240,7 @@
<h2 id="sending-scheduled-events">Sending Scheduled Events</h2>
<p>Scheduled events are OSGi events that have been created by the environemnt.
They are generated on each application node of the cluster through an own
scheduler instance. Sending these events works the same as sending events based
on JCR events (see above).</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1505925 by cziegeler on Tue, 23 Jul 2013 07:58:25 +0000
+ Rev. 1550766 by rombert on Fri, 13 Dec 2013 16:46:20 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
