public class DetailsDateUtility
extends java.lang.Object
LOCAL_OFFSET
+00:00. This is because we must provide an offset when
creating OrderValidityDate.parse(String, String, String, String)
or OrderValidityDate.parse(String, String, String, String)
.
when using 'Local'.
It is possible to provide a proper offset when creating an ActivationDate or ExpirationDate using client data. But when creating the same objects from RET, We cannot obtain this offset. The date and time we provide to these methods are in UTC/GMT.
The front end will need to take into account that dates with the location as 'Local' and offset +00:00 coming from the server must be converted back to the original date using it's own local offset.
Constructor and Description |
---|
DetailsDateUtility() |
Modifier and Type | Method and Description |
---|---|
static void |
addActivationDate(com.caplin.motif.fx.trading.orders.details.StrategyFieldSet fixedFields,
com.caplin.ret.trapi.fx.FXOrder order) |
static void |
addExpirationDate(com.caplin.motif.fx.trading.orders.details.StrategyFieldSet fixedFields,
com.caplin.ret.trapi.fx.FXOrder order) |
public static void addActivationDate(com.caplin.motif.fx.trading.orders.details.StrategyFieldSet fixedFields, com.caplin.ret.trapi.fx.FXOrder order) throws com.caplin.motif.fx.trading.orders.OrderConfigurationException
com.caplin.motif.fx.trading.orders.OrderConfigurationException
public static void addExpirationDate(com.caplin.motif.fx.trading.orders.details.StrategyFieldSet fixedFields, com.caplin.ret.trapi.fx.FXOrder order) throws com.caplin.motif.fx.trading.orders.OrderConfigurationException
com.caplin.motif.fx.trading.orders.OrderConfigurationException
Copyright © 2019 Caplin Systems.