Custom Logon Configuration in Config File

Version 1 by Marc Hodgins
on May 23, 2009 00:58.

compared with
Current by Marc Hodgins
on May 23, 2009 01:00.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View page history
(... and then the RawDataLength field would be calculated automatically).
This would make it possible to use Quickfix via the Apache Synapse / the WSO2 ESB (Enterprise Service Bus).  As it stands, it is impossible to use Quickfix and Synapse/WSO2ESB with counterparties that require custom logons because the logon process happens before it is possible to mediate (change) the contents of the messages that QuickFIX is emitting.  There is no clean way to Quickfix via Java on this platform so it is absolutely essential that these custom options can be specified in the configuration file rather than via java callbacks.
This would make it possible to use Quickfix via the Apache Synapse / the WSO2 ESB (Enterprise Service Bus).  As it stands, it is impossible to use Quickfix and Synapse/WSO2ESB with counterparties that require custom logons because the logon process happens before it is possible to mediate (change) the contents of the messages that QuickFIX is emitting.  There is no way on those platforms (except possibly writing some complex wrapper code around Quickfix, or modifying the Quickfix source and rebuilding the jar) to interface with Quickfix's callbacks and allow custom logons.  So, it is absolutely essential that these custom options can be specified in the configuration file rather than via java callbacks.