-
Epic
-
Resolution: Obsolete
-
Major
-
None
-
5.3.7
-
-
Redesign action capabilities
-
Empty show more show less
Current implementation of async actions for multiple items must be improved.
- Class hierarchy is inconvenient
- AbstractAction => AbstractMultiItemAction => AbstractCommandAction (which historically states it should not be called for multiple items)
- This makes it very difficult for an action to compose such capabilities.
- Notifications do not work well w/ async and multiple items
- see
MGNLUI-3341for more symptoms
- see
- Async support is not really async
- UI may still be blocked while supposedly async action execution takes place
- We should reconsider
hijackusage of scheduler in there - Proper async support depends on servlet 3; we need to evaluate consequences (e.g. on filters/filter chain) and build this appropriately
- Push alone won't solve those issues for us
Other points which may be revisited:
- Availability (esp. towards multi-item)
- Callback hell, exposing more context, params, UI components to actions & save actions
- is depended upon by
-
MAGNOLIA-6246 Send and show fewer messages when deleting multiple items at once
- Open
-
MGNLUI-3606 Batch actions for publishing, duplicating, exporting, downloading, renaming items
- Closed
-
MGNLUI-3585 Action bar is not well structured when there are many actions
- Closed
- is related to
-
MGNLUI-3341 Avoid multiple asynchronous tasks and pulse messages when deleting multiple items at once
- Closed
- relates to
-
MAGNOLIA-6560 Isolation level of MarkNodeAsDeleted is not sufficient - Possible data loss
- Closed
- supersedes
-
MGNLUI-3107 Publishing deletion right after delete can result in exception
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...