org.alfresco.bm.driver.event.producer

Class RandomRedirectEventProducer

java.lang.Object

org.alfresco.bm.driver.event.producer.AbstractEventProducer

org.alfresco.bm.driver.event.producer.RandomRedirectEventProducer

All Implemented Interfaces:

EventProducer, org.springframework.beans.factory.Aware, org.springframework.beans.factory.BeanNameAware

public class RandomRedirectEventProducer
extends AbstractEventProducer

Redirect events randomly based on relative weights.

A weighted selection algorithm is used.

Since:

2.0

Author:

Steve Glover, Derek Hulley

See Also:

EventWeight, RandomWeightedSelector

Field Summary

Fields inherited from class org.alfresco.bm.driver.event.producer.AbstractEventProducer

DEFAULT_AUTO_CLOSE_SESSION_ID, DEFAULT_AUTO_PROPAGATE_SESSION_ID, DEFAULT_CHART, DEFAULT_WARN_DELAY, logger

Fields inherited from interface org.alfresco.bm.driver.event.producer.EventProducer

PRODUCER_NAME_PREFIX

Constructor Summary

Constructors

Constructor and Description
RandomRedirectEventProducer(List<EventWeight> eventWeights)

Method Summary

Modifier and Type	Method and Description
List<Event>	getNextEvents(Event event) Construct a list of events to follow according the some scenario of business logic.

Methods inherited from class org.alfresco.bm.driver.event.producer.AbstractEventProducer

register, resumeTimer, setBeanName, setEventName, setEventNames, setRegistry, stopTimer, suspendTimer, toString

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Constructor Detail

RandomRedirectEventProducer

public RandomRedirectEventProducer(List<EventWeight> eventWeights)

Parameters:

eventWeights - list of events weights to select from

Method Detail

getNextEvents

public List<Event> getNextEvents(Event event)

Description copied from interface: EventProducer

Construct a list of events to follow according the some scenario of business logic.

Implementations use the contextual data available to determine the next course of action. However, the no-op (empty list return) should be determined as quickly and cheaply as possible.

NB: Implementations must ensure that an adequate termination condition exists and return an empty list. If not, an infinite loop of events can ensue.

Parameters:

event - the event that triggered this choice

Returns:

a list of events to publish (never null) or an empty list if the scenario cannot continue