[MGNLWORKFLOW-213] Need help regarding persistence of workflow state Created: 25/Feb/14 Updated: 03/Mar/14 Resolved: 03/Mar/14 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | jBPM |
| Affects Version/s: | 5.2.2 |
| Fix Version/s: | 5.3 |
| Type: | Task | Priority: | Major |
| Reporter: | Dean Pullen | Assignee: | Espen Jervidalo |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoR: |
Empty
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
I have extended the workflow to split approval/publish into two different tasks. However, if I restart the server after approving (and pre-publishing) the state is lost. I notice in JcrPersistingProcessEventListener that the process state is persisted in beforeProcessCompleted/afterProcessCompleted when a process is started/finished. However, for each individual task, how do we persist the process? I've extended JcrPersistingProcessEventListener and persisted via afterNodeTriggered which does ultimately work, but is this the correct way? It's obviously called many more times than required as it's after ever ndoe trigger. |
| Comments |
| Comment by Dean Pullen [ 26/Feb/14 ] |
|
Sorry, this has been raised under support. |
| Comment by Espen Jervidalo [ 03/Mar/14 ] |
|
Persistence has been rewritten as part of magnolia 5.3. See linked ticket. |