Platform Explorer / Nuxeo Platform 2023.12



The WorkManager executes Work instances asynchronously.

Resolution Order

The resolution order represents the order in which this component has been resolved by the Nuxeo Runtime framework.
You can influence this order by adding "require" tags in your component declaration, to make sure it is resolved after another component.

Start Order

9 (Declared Start Order: -501)
The start order represents the order in which this component has been started by the Nuxeo Runtime framework.
This number is interesting to tweak if your Java component interacts with other components, and needs to be started before or after another one.
It can be changed by implementing the method "Component#getApplicationStartedOrder()" on your Java component: components are sorted according to this reference value, in increasing order.
The default value is 1000, and the repository initialization uses number 100. Negative values can also be used.




Extension Points

XML Source

<?xml version="1.0"?>
<component name="" version="1.0">

    The WorkManager executes Work instances asynchronously.

    <provide interface="" />

  <implementation class="" />

  <extension-point name="queues">
      Defines the characteristics of work queues:
        <queue id="myqueue">
          <name>My Queue</name>
      - id is the queue id.

      - name is the human-readable name.

      - maxThreads maximum number of worker threads (default 4).

      - capacity when specified make the queue bounded, the scheduling of
      new work is blocking when the queue is full (default unlimited).

      - clearCompletedAfterSeconds (default 3600) is the delay after which completed work
       may be automatically cleared from its queue. 0 means never.

      - category is a list of Work categories that this queue will receive.
      For event listeners work, the category is the listener name (or its simple class name).

    <object class="" />

  <extension-point name="implementation">
      Defines the implementation of the queuing mechanism:
        <queuing class=""/>
      The class must be a subclass of

      Not used since 2023 since Redis support has been removed, only the in memory implementation remains which is used
      for testing. Otherwise, StreamWorkManager is the WorkManager implementation to use and it doesn't use queuing.

    <object class="" />