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.doneIt 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.SessionService
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,
org.apache.commons.lang3.time.StopWatch stopWatch)
Process an event.
|
void |
propagateSessionId(Event event,
Event nextEvent)
Carry session IDs from the executed event to all the new event.
|
long getWarnDelay()
boolean isChart()
EventResult processEvent(Event event, org.apache.commons.lang3.time.StopWatch stopWatch) throws Exception
StopWatch.start()
and StopWatch.stop()
the timer to better reflect actual event processing.event
- the event (along with associated data)stopWatch
- the timer that will be used or null to have one
created and attached to the process automaticallyException
void propagateSessionId(Event event, Event nextEvent)
SessionService
to initiate a new session
and put that into the next event. Otherwise they can choose to terminate sessions
and remove session IDs from the next event(s).event
- the original eventnextEvent
- a new event (possibly one of many)Copyright © 2014. All rights reserved.