Re: [Quickfixj-users] acceptor

[Steve B. <st...@te...>]

> Thanks for the quick and thorough reply Steve!  The other problem I
> encountered is we're using Java 1.4.2...but I think I can convince them
> to upgrade to Java 5 for the FIX servers at least.  Domino effect!

I've committed changes to the related JDBC log and store implementations
to the QFJ SVN trunk. If you need to patch your installation you can see
the files that changed in SVN by looking at the Subversion link in the
JIRA issue (QFJ-295). I'll update the documentation later for the new
setting.

> Intervening on the source code is slightly problematic for upgrades for
> us because we're also using an extended FIX42.xml data dictionary file
> as well (which already requires me to unjar the 42 library and replace
> the data dictionary with our extended version and then re-jar it)...
> that contains the following two additional entries for liquidity for
> Nasdaq and DirectEdge who unfortunately use the same custom liquidity
> tag and for ARCA:

Given the trouble, why do you put the data dictionary in the JAR file?
It will be picked up anywhere in the class path. For example, it could
be in your application JAR or in a well-known location in the file
system. If you name your data dictionary something like FIX42-DirectEdge.xml
then you won't have to worry about accidentally picking up the FIX42.xml
in the QFJ jars.

> <field number="9882" name="INETLiquidity" type="CHAR">
> ...

If you add the attribute allowOtherValues="Y" to your field definition
then you won't have to include the undefined values for validation purposes.
This was added in a recent release (1.3.0, I think, but it might have been
in 1.3.1).

For example...

<field number="9882" name="INETLiquidity" type="CHAR" allowOtherValues="Y">

Regards,

Steve