Class DetailsDateUtility

  • public class DetailsDateUtility
    extends java.lang.Object
    When location is 'Local' we set offset to 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.

    • Method Summary

      All Methods Instance Methods Concrete Methods 
      Modifier and Type Method Description
      void addActivationDate​( fixedFields, com.caplin.ret.trapi.fx.FXOrder order)  
      void addExpirationDate​( fixedFields, com.caplin.ret.trapi.fx.FXOrder order)  
      • Methods inherited from class java.lang.Object

        equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
    • Constructor Detail

      • DetailsDateUtility

        public DetailsDateUtility()
    • Method Detail

      • addActivationDate

        public void addActivationDate​( fixedFields,
                                      com.caplin.ret.trapi.fx.FXOrder order)
      • addExpirationDate

        public void addExpirationDate​( fixedFields,
                                      com.caplin.ret.trapi.fx.FXOrder order)