You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Currently the Action interface in decision maker has an execute() method. The original idea being that publisher would just invoke execute on each action. However, different scenarios/systems can have different requirements for execute.
We want to decouple action and their execution. Create a listener interface which allows developers to create different ways of handling actions published by the Publisher. We register these listeners with the publisher, and each of them get invoked when an action is published.
The text was updated successfully, but these errors were encountered:
Currently the
Action
interface in decision maker has anexecute()
method. The original idea being that publisher would just invoke execute on each action. However, different scenarios/systems can have different requirements for execute.We want to decouple action and their execution. Create a listener interface which allows developers to create different ways of handling actions published by the Publisher. We register these listeners with the publisher, and each of them get invoked when an action is published.
The text was updated successfully, but these errors were encountered: