| 1 |
<?xml version="1.0"?> |
|---|
| 2 |
|
|---|
| 3 |
<component name="org.nuxeo.ecm.core.lifecycle.LifeCycleService"> |
|---|
| 4 |
|
|---|
| 5 |
<documentation> |
|---|
| 6 |
Service that deals with life cycle. |
|---|
| 7 |
|
|---|
| 8 |
@version 1.0 |
|---|
| 9 |
@author <a href="mailto:ja@nuxeo.com">Julien Anguenot</a> |
|---|
| 10 |
</documentation> |
|---|
| 11 |
|
|---|
| 12 |
<implementation class="org.nuxeo.ecm.core.lifecycle.impl.LifeCycleServiceImpl"/> |
|---|
| 13 |
|
|---|
| 14 |
<extension-point name="lifecycle"> |
|---|
| 15 |
|
|---|
| 16 |
<documentation> |
|---|
| 17 |
Extension point for registering life cycle definition. |
|---|
| 18 |
|
|---|
| 19 |
<p/> |
|---|
| 20 |
|
|---|
| 21 |
A life cycle is a state-transition model described as an XML document. |
|---|
| 22 |
|
|---|
| 23 |
<p/> |
|---|
| 24 |
|
|---|
| 25 |
A life cycle within Nuxeo Core describes only the states and the transitions |
|---|
| 26 |
without any security policy whatsoever. For instance, the workflow service |
|---|
| 27 |
(or BPM service) will be responsible of the security policy and actors |
|---|
| 28 |
involved. |
|---|
| 29 |
|
|---|
| 30 |
</documentation> |
|---|
| 31 |
|
|---|
| 32 |
<object class="org.nuxeo.ecm.core.lifecycle.extensions.LifeCycleDescriptor"/> |
|---|
| 33 |
|
|---|
| 34 |
</extension-point> |
|---|
| 35 |
|
|---|
| 36 |
<extension-point name="lifecyclemanager"> |
|---|
| 37 |
|
|---|
| 38 |
<documentation> |
|---|
| 39 |
Extension point for registering life cycle manager. |
|---|
| 40 |
|
|---|
| 41 |
<p/> |
|---|
| 42 |
|
|---|
| 43 |
Life cycle manager are responsible of the life cycle properties storage and |
|---|
| 44 |
are bound to a life cycle. |
|---|
| 45 |
|
|---|
| 46 |
<p/> |
|---|
| 47 |
|
|---|
| 48 |
Nuxeo core default life cycle manager is a JCR life cycle manager. It means |
|---|
| 49 |
the life cycle properties for a given document will be stored in the JCR |
|---|
| 50 |
along with the other document properties. You may define another type of |
|---|
| 51 |
life cycle manager such as an SQL life cycle manager that would store the |
|---|
| 52 |
life cycle properties in a SQL DB aside the JCR. |
|---|
| 53 |
|
|---|
| 54 |
<p/> |
|---|
| 55 |
|
|---|
| 56 |
The life cycle properties are : |
|---|
| 57 |
|
|---|
| 58 |
<ul> |
|---|
| 59 |
<li><i>currentLifeCycleState</i> : the current life cycle state</li> |
|---|
| 60 |
<li><i>lifeCyclePolicy</i> : the life cycle policy applied</li> |
|---|
| 61 |
</ul> |
|---|
| 62 |
|
|---|
| 63 |
</documentation> |
|---|
| 64 |
|
|---|
| 65 |
<object class="org.nuxeo.ecm.core.lifecycle.extensions.LifeCycleManagerDescriptor"/> |
|---|
| 66 |
|
|---|
| 67 |
</extension-point> |
|---|
| 68 |
|
|---|
| 69 |
<extension-point name="types"> |
|---|
| 70 |
|
|---|
| 71 |
<documentation> |
|---|
| 72 |
Extension point for registering document type to life cycle mappings. |
|---|
| 73 |
|
|---|
| 74 |
<p/> |
|---|
| 75 |
For instance, you can specify that a documen type <i>File</i> will follow a |
|---|
| 76 |
<i>default</i> life cycle where <i>default</i> is the name of a registered |
|---|
| 77 |
life cycle. |
|---|
| 78 |
|
|---|
| 79 |
</documentation> |
|---|
| 80 |
|
|---|
| 81 |
<object class="org.nuxeo.ecm.core.lifecycle.extensions.LifeCycleTypesDescriptor"/> |
|---|
| 82 |
|
|---|
| 83 |
</extension-point> |
|---|
| 84 |
|
|---|
| 85 |
</component> |
|---|