-
Type: Task
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 5.1.5
-
Fix Version/s: 5.1.6
-
Component/s: None
-
Impact type:Configuration format change
-
Upgrade notes:
Currently the lifecycles depend on a given lifecycle manager, of which we only have a single implementation: JCRLifeCycleManager.
The specification of which lifecycle manager implementation (which decides how to store lifecycle policy and state in a document) should be global instead of per-lifecycle, so that the same lifecycles can be used with a non-JCR backend.
TODO:
nuxeo-core's LifeCycleCoreExtensions.xml and nuxeo-platform-forum-core's forum-schemas-contrib.xml have dependencies on JCRLifeCycleManager which should be removed.
The references to jcrlifecyclemanager from lifecycles should be made unnecessary, and only one lifecycle manager allowed at a time (lifecyclemanager extension point of org.nuxeo.ecm.core.lifecycle.LifeCycleService).
LifeCycleServiceImpl should only instantiate a single manager for all lifecycles.
- is required by
-
NXP-2514 Implement SQL storage backend
- Resolved