com.caplin.motif.fx.trading.orders.submission.event

Class OrderAcceptEvent

java.lang.Object

com.caplin.motif.trading.ResponderEvent<MotifTrade>

com.caplin.motif.fx.trading.orders.submission.event.OrderAcceptEvent

All Implemented Interfaces:

BaseResponderEvent

public class OrderAcceptEvent
extends ResponderEvent<MotifTrade>

An event to notify the client that the submission of the order or order strategy has been completed, and the order (or orders) is now active.

See Also:

OrderPendingAcceptResponder.sendAccept(OrderAcceptEvent)

Field Summary

Fields

Modifier and Type	Field and Description
static String	ACCEPT_EVENT The name of the transition representing this event

Fields inherited from class com.caplin.motif.trading.ResponderEvent

fields

Constructor Summary

Constructors

Constructor and Description
OrderAcceptEvent(List<String> orderIDs) Creates an OrderAcceptEvent with the event name "Accept" and multiple order IDs.
OrderAcceptEvent(String orderID) Creates an OrderAcceptEvent with the event name "Accept" and the provided order ID.

Method Summary

Methods inherited from class com.caplin.motif.trading.ResponderEvent

addField, addFields, addTransparentFields, equals, getEventName, getField, getFields, hashCode, toString

Methods inherited from class java.lang.Object

clone, finalize, getClass, notify, notifyAll, wait, wait, wait

Field Detail

ACCEPT_EVENT

public static final String ACCEPT_EVENT

The name of the transition representing this event

See Also:

Constant Field Values

Constructor Detail

OrderAcceptEvent

public OrderAcceptEvent(String orderID)

Creates an OrderAcceptEvent with the event name "Accept" and the provided order ID.

Parameters:

orderID - The order id to send (usually the parent order ID).

OrderAcceptEvent

public OrderAcceptEvent(List<String> orderIDs)

Creates an OrderAcceptEvent with the event name "Accept" and multiple order IDs. This is used when a multi-order strategy has been accepted.

Parameters:

orderIDs - The order IDs of each of the orders in the strategy. The list must be ordered according to the semantics of the strategy, for example if the strategy is an IfDoneOCOStrategy the first order ID in the list should be the parent order ID, followed by the two order IDs for the OCO part of the strategy. This list will be sent as a comma separated string on the field "OrderID".