Here is a quick example showing how to use Log4FIX in live mode and the standard QuickFIX/J file log.
SessionSettings settings = ...
Log4FIX forLiveUpdate = Log4FIX.createForLiveUpdates(settings);
LogFactory log4FIXLogFactory = forLiveUpdate.getLogFactory();
LogFactory fileLogFactory = new FileLogFactory(settings);
// create a composite containing the Log4FIX LogFactory
// and the FileLogFactory
LogFactory compositeLogFactory = new CompositeLogFactory(new LogFactory[] {
log4FIXLogFactory, fileLogFactory});
initiator = new SocketInitiator(..., ..., ..., compositeLogFactory, ...);
...
// show the Log4FIX panel
forLiveUpdate.show();
Your QuickFIX/J application now sends log messages to Log4FIX and to a file.
Enjoy.
June 28th, 2007
I am pleased to announce Log4FIX 1.6. This release fixes a threading bug that swallowed error messags, and adds the capability to automatically import a single file from the command line.
Listed below are the links to the issues resolved in this release:
Here is an example showing how to tell Log4FIX to automatically import a log file when starting Log4FIX:
$ java -jar log4fix-1.6.jar /path/to/my_data.log
Thanks to all that help make Log4FIX a better product.
March 6th, 2007
I am excited to announce the release of Log4FIX 1.5. There are two new features in this release:
February 3rd, 2007
We are attempting to capture various tasks using our project’s Google Code Issue Tracker.
Where’s The Code?
We are not releasing the code until we have a solid foundation good enough to call “beta”. There are several reasons. Arguably the most important reason is due to the constant code changes. The APIs have dramatically changed in just a few days. Thus you would become quite angry with us as we pull the API carpet out from under your feet.
Is There a Roadmap?
Unfortunately we do not have a roadmap (yet). We’ll post the roadmap as soon as possible. In the meantime, feel free to keep tabs on the Google Code Issue Tracker. Feel free to add feature requests to the list.
January 30th, 2007
Currently this site discusses a single application called Log4FIX, which is a great tool for viewing raw FIX messages in real-time as part of your QuickFIX/J application, or later using any file containing raw FIX messages. Very soon more details will emerge about another product named OpenOMS. OpenOMS is an order management system based on a FIX engine. Of course, OpenOMS will “ship” configured for QuickFIX/J. A major goal of OpenOMS is to fill the gap between your trading algorithms and order management. QuickFIX/J provides FIX connectivity. OpenOMS manages your orders. You concentrate on your trading algorithms.
Are there other open source trading applications or tools that you would like to bring to this site? If so, let me know. We can talk.
January 23rd, 2007
I moved Log4FIX from SourceForge.net to Googe Code. SourceForge, in my opinion, is slow, clunky, and hard to use. So far I have enjoyed my experiences with Google Code.
http://code.google.com/p/log4fix/
January 6th, 2007
I am pleased to announce the release of Log4FIX 1.0. This release includes numerous bug fixes, enhanced memory management, and updated message logging.
Please visit http://code.google.com/p/log4fix/ for more information.
January 6th, 2007
If you are running Windows, and Log4FIX is not rendered with the Windows Look-N-Feel, then execute Log4FIX like this:
- $ java -Dswing.defaultlaf=com.sun.java.swing.plaf.windows.WindowsLookAndFeel -jar log4fix-1.0.jar
December 27th, 2006
You may have noticed that the RSS feed links are broken. Sorry! Please update your feeds to the new address. The links changed when I moved this site from Yahoo! Web Hosting to my firm’s hardware. Object Computing, Inc. (OCI) has graciously provided hardware and bandwidth for this site.
December 21st, 2006
User defined fields are allowed by the FIX protocol to provide maximum flexibility for institutitions. I wrote an article, published by Object Computing, Inc. (OCI), describing various ways to create FIX messages with user defined fields in QuickFIX/J.
July 1st, 2006