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.

Listed below are the links to the issues resolved in this release:

• Launch Log4FIX and Automatically Import a Log File
• Log4FIX Stops Processing The Log File With No Explanation

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.

• Filter Out Heartbeat Messages
• Capability To Reverse The Raw Message Table View

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.

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.

http://code.google.com/p/log4fix/

Please visit http://code.google.com/p/log4fix/ for more information.