Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-3398

Redesign action capabilities: multi-item, command-based, asynchronous

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 5.3.7
    • framework
    • Redesign action capabilities

      Current implementation of async actions for multiple items must be improved.

      1. 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.
      2. Notifications do not work well w/ async and multiple items
      3. Async support is not really async
        • UI may still be blocked while supposedly async action execution takes place
        • We should reconsider hijack usage 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:

      1. Availability (esp. towards multi-item)
      2. Callback hell, exposing more context, params, UI components to actions & save actions

        Acceptance criteria

              Unassigned Unassigned
              cmeier Christoph Meier
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: