[MGNLWORKFLOW-185] JCR stored ProcessInstances are never updated Created: 16/Dec/13 Updated: 19/Dec/13 Resolved: 17/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | None |
| Affects Version/s: | 5.2 |
| Fix Version/s: | 5.2.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Description |
|
Our current implementation stores newly created ProcessInstances (state = ProcessInstance.STATE_PENDING) but never updates them. In JPA implementation this is done via transaction managers. We should implement similar behavior for JCR storage. As TransactionManagers (at least the jbpm 5.4.x ones) seem to be tight to JPA already it could also be best to implement updating using ProcessEventListeners |