public interface EventProcessor
result of event processing
does not have to contain any further events. However, it is better to publish a 'finished' event
as it allows more flexibility in wiring test scenarios together.
start -> doA -> doB -> doB.done
It is possible to remap doB.done above back into doA and thereby create an
test that never ends, for example.
data the input event must
the event contain), likely actions and the possible output e.g.| Modifier and Type | Method and Description |
|---|---|
long |
getWarnDelay()
Provide a hint for the processing framework on how much time should elapse before
the warnings need to be issued over the delay
|
boolean |
isChart()
Hint whether the result should be included in charts
|
EventResult |
processEvent(Event event)
Process an event.
|
long getWarnDelay()
boolean isChart()
EventResult processEvent(Event event) throws Exception
event - the event (along with associated data)ExceptionCopyright © 2012. All Rights Reserved.