Class DetailsDateUtility
- java.lang.Object
-
- com.caplin.motif.fx.ret.orders.extension.details.DetailsDateUtility
-
public class DetailsDateUtility extends java.lang.Object
When location is 'Local' we set offset toLOCAL_OFFSET
+00:00. This is because we must provide an offset when creatingOrderValidityDate.parse(String, String, String, String)
orOrderValidityDate.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 Summary
Constructors Constructor Description DetailsDateUtility()
-
Method Summary
All Methods Static Methods Concrete Methods Modifier and Type Method 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)
-
-
-
Method Detail
-
addActivationDate
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
- Throws:
com.caplin.motif.fx.trading.orders.OrderConfigurationException
-
addExpirationDate
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
- Throws:
com.caplin.motif.fx.trading.orders.OrderConfigurationException
-
-