[MAGNOLIA-1070] JCRExpressionStore contentIterator broken Created: 21/Sep/06 Updated: 03/Oct/06 Resolved: 03/Oct/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | workflow |
| Affects Version/s: | 3.0 RC2 |
| Fix Version/s: | 3.0 RC3 |
| Type: | Bug | Priority: | Major |
| Reporter: | John Mettraux | Assignee: | John Mettraux |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 6d | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | 6d | ||
| Environment: |
any |
||
| 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 |
|
The workflow / JCRExpressionStore contentIterator seem broken. The symptom : on restarts of Magnolia, activation scheduled per workflow are not taken into account. Log analysis revelead that the embedded workflow engine attempts at retrieving expressions to reschedule, but the JCRExpressionStore contentIterator returns none. My company grants me two days to work on that issue. |
| Comments |
| Comment by John Mettraux [ 03/Oct/06 ] |
|
Fixed the content iterator and did some code cleanup. |