[WW-4883] Action invocation and result execution should not being coupled

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: Core, Core Actions, Core Results
• Labels: decouple
• Assignee: Unassigned
• Reporter: Yasser Zamani
• Created: 23/Oct/17 12:33
• Updated: 17/Oct/22 05:25
• Resolved: 17/Oct/22 05:25

Description

For example DefaultActionInvocation class not only invokes action but also calls pre-result listeners and executes result. Such design is not good when for example action invocation and result execution are asynchronous to each other.

Issue Links

• is required by: WW-4874 Asynchronous action method