As an example, a "submit" event might signal that a Submit button was pressed in a web browser. A "success" event might signal an action executed successfully. A "finish" event might signal a subflow ended normally.
Why is this not an interface? A specific design choice. An event is not a strategy that defines a generic type or role--it is essentially an immutable value object. It is expected that specializations of this base class be "Events" and not part of some other inheritance hierarchy. @author Keith Donald @author Erwin Vervaet @author Colin Sampaleanu
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|