Re: [Quickfixj-users] acceptor

[Robert B. <rbr...@me...>]

Thanks so much for your help Steve...this is great!

robert l. brueckmann
vice president
merlin securities
712 fifth avenue
new york, ny 10019
p: 212.822.4821
f: 212.822.4820



Merlin Securities - #1 Prime Broker North America and #1 Prime Broker Single Strategy Funds - Global Custodian 2007
#1 Prime Broker for Hedge Funds under $1 Billion - Alpha Survey 2007



From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Steve Bate
Sent: Monday, February 04, 2008 1:17 PM
To: qui...@li...
Subject: Re: [Quickfixj-users] acceptor

QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/


> 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



------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Quickfixj-users mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
 

--------------------------------------------------------

This message contains information from Merlin Securities, LLC, or from one of its affiliates, that may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify the sender immediately by telephone or by replying to this transmission.
 
Merlin Securities, LLC is a registered broker-dealer. Services offered through Merlin Securities, LLC are not insured by the FDIC or any other Federal Government Agency, are not deposits of or guaranteed by Merlin Securities, LLC and may lose value. Nothing in this communication shall constitute a solicitation or recommendation to buy or sell a particular security.