Vid and Claus,
QuickFIX/J currently loads the settings file by itself. The SessionSettings
class interface isn't a great fit for direct usage in an IoC framework but
we could investigate some type of adapter (e.g., a Spring factory bean) that
would allow it to be configured and injected into the component. I'm
assuming the ideal approach would support any IoC framework. I'd have to do
some experimentation to determine the feasibility of doing that.
The SessionSettings class does have its own simple property placeholder
capability. For example, a Properties object could be injected into the
quickfix component and that could be used to interpolate value placeholders
in the settings file.
For example, in the following settings file snippet the sender and target
will use substitutions from a supplied Properties object.
...
[SESSION]
BeginString=FIX.4.2
SenderCompID=${sender}
TargetCompID=${target}
...
Thoughts?
Steve
On 11/10/10 2:51 AM, "Claus Ibsen" <claus.ib...@gmail.com> wrote:
> What if QuickFix allows IoC for its configuration. Then you have a
> much wider choice.
> I don't know if QuickFix mandates and loads the config file entirely by
> itself.
>
>
>
> On Tue, Nov 9, 2010 at 11:31 PM, vcheruvu <v_cher...@hotmail.com> wrote:
>>
>> Camel Riders,
>>
>> Any thoughts to my second question on utilizing Camel property placeholder
>> for Quickfixj component's config files.I believe it will simplify config
>> file management and centralize all the environment specific values.
>>
>> Kind regards,
>> -Vid-
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Camel-quickfix-logging-tp3249378p3257801.ht
>> ml
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>
