-
Story
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
Current implementation of activation doesn't seem very robust and is nested very deep making it difficult to evaluate impact of any changes. Also as it is concurent activation is effectively prevented by enforced synchronization and other implementation details.
- depends upon
-
MAGNOLIA-2055 Activation should report an error when the activating user can't login
- Closed
-
MAGNOLIA-2056 Activation: 401s are ignored or not reported when activating a single page
- Closed
-
MAGNOLIA-2121 activation: use a thread per subscriber
- Closed
- is related to
-
MAGNOLIA-2411 Provide a minimal set of automated integration tests
- Closed
-
MGNLXAA-3 Cleanup of CopyUtil.
- Closed