Discussion Forums

Choices in your Java-FIX knowledge & learning intersection
Mahesh Kumaraguru <>
15 Dec 2005 1:57AM ET

Hello sindhu priya,

These are the two choices in your Java-FIX knowledge & learning intersection :-

1) Take the "QuickFix" route - it would get you working fast.

2) Take the start from scratch route - build everything you need in Java or any other language which has required capabilities, refer -

http://fixprotocol.org/discuss/read/68c3e5d1

If you take route 2), you will "get yourself all dirty" with FIX - I liked this approach - Debugging thru FIX 4.2 logs which have ASCII SOH chars which display as a box in notepad. I started on this route because for me a FIX engine was part of a much bigger scheme - a framework for end to end automated testing of financial instruments trading applications which use FIX protocol.

This choice also depends on what your requirement is. Since my FIX engine is used as part of a testing sequence, I wanted to be able to send "invalid FIX messages" like a message with an incorrect checksum or a message with an invalid body length etc. Since it was not clear from the documentation of open source Java FIX projects how much tweaking / code changes are required to get these kind of non-FIX flexibilities, I decided to pursue "develop from scratch" approach.

Since mine was a "proof of concept" project, I handled only FIX 4.2 messages tag=value<SOH> in the FIX part ( In a different part I have done Java-FIXML using Java-XML tools ). The other parts like order generation system generate messages in other formats like positional fields / flat Cobol record etc and use different communication technologies like Messaging. I have built my own Java FIX tools like JMS<->TCP and TCP<->JMS FIX adapters, convertor to convert from one version of FIX to another and back, exchange simulator, distributed end to end FIX tester, a structure for a FIX message store and a query language for querying this message store, etc - These are all part of "my experiments with FIX" :-)

Regards,
K. Mahesh

> hello thanks for your reply.i also plan to develop the fixml in java.
>
>


guidance for me to develop fixml
sindhu priya   12 Dec 2005 6:12PM ET
Re: guidance for me to develop fixml
Mahesh Kumaraguru   13 Dec 2005 1:27PM ET
Re: guidance for me to develop fixml
Calvin Lai   13 Dec 2005 2:36PM ET
Re: guidance for me to develop fixml
Mahesh Kumaraguru   13 Dec 2005 3:32PM ET
Re: guidance for me to develop fixml
sindhu priya   14 Dec 2005 12:01PM ET
Developing FIX engine in Java for FIXML.4.4
Mahesh Kumaraguru   14 Dec 2005 12:32PM ET
Re: guidance for me to develop fixml
Jörg Thönnes / Macdonald Associates   14 Dec 2005 12:50PM ET
Choices in your Java-FIX knowledge & learning intersection
Mahesh Kumaraguru   15 Dec 2005 1:57AM ET