Timed activation
(MGNLWORKFLOW-126)
|
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | Base |
| Affects Version/s: | 5.2.1 |
| Fix Version/s: | 5.3 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Espen Jervidalo | Assignee: | Espen Jervidalo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Our JCR persistency is not complete. It does not store the session used to reactivate timers when restarting the system. |
| Comments |
| Comment by Espen Jervidalo [ 21/Jan/14 ] |
|
resolved on jcr-persistence-integration branch |
| Comment by Daniel Lipp [ 22/Jan/14 ] |
|
workflow-nodetypes.xml still defines a nodeType mgnl:kSession. Also we should not place the persistence code in org.jbpm and org.drools but in info.magnolia.jbpm and info.magnolia.drools packages. |
| Comment by Espen Jervidalo [ 22/Jan/14 ] |
|
The nodeType changes are already in progress under Concerning packaging, I discussed this with greg. This is the best approach so far. Only thing he wanted to avoid is spoiling the groupId and artifacts in maven, which is now under our workflow groupId and so on. Apart from that, there are lots of protected fields which are only accessible from same package and considering the possibility to get it integrated upstream makes it much easier doing it the right way from the beginning. |