All Classes
| Class | Description |
|---|---|
| Activatable |
Interface for services that need to be called when the final
TimeslotComplete message has been received from the server
in each timeslot.
|
| BrokerContext |
Provides message handler registration, along with
access to competition context information, including
The message router for outgoing messages
The underlying org.powertac.common.Broker instance
The name of this broker
The base time for the current simulation
The length of common data arrays
|
| BrokerMain |
This is the top level of a Power TAC broker implementation.
|
| BrokerMessageReceiver |
Receives incoming jms messages for the broker and deserializes them just in case they are to be consumed within the
current JVM process.
|
| BrokerPropertiesService |
Supports annotation-based configuration of broker components from
properties or xml config files.
|
| BrokerRunner |
Multi-session broker runner.
|
| BrokerTournamentService |
Logs a broker into a tournament server, retrieving tournament-specific
and game-specific configuration data from the server.
|
| Initializable |
Implementations of this interface have their initialize() methods called
at the appropriate point in the broker startup sequence.
|
| IpcAdapter |
Implementations are intended to allow out-of-process broker implementation
through an inter-process communication path.
|
| JmsManagementService |
Manages the JMS connection to a simulation server.
|
| MessageDispatcher |
Routes incoming messages to broker components, and outgoing messages
to the server.
|
| PowerTacBroker |
This is the top-level controller for a single broker session.
|