[
https://issues.apache.org/activemq/browse/CAMEL-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Beat Glattfelder updated CAMEL-2536:
------------------------------------
Attachment: camel-quickfix.zip
> Improved quickfix component
> ---------------------------
>
> Key: CAMEL-2536
> URL: https://issues.apache.org/activemq/browse/CAMEL-2536
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: Beat Glattfelder
> Attachments: camel-quickfix.zip
>
>
> Looking into rewriting our Java based order routing system using camel, I ran
> into several issues with the camel-quickfix component that comes with 2.1.0.
> I therefore wrote a new component based on the quickfix driver code from our
> old app, and successfully ported our system. I would be very glad to
> contribute the improved component to the project, so please have a look
> whether you think it's usable.
> The main features are:
> The quickfix endpoint URL identifies a FIX session through its quickfix
> seesion id which is based on the sessions CompIds, thus allowing the setup of
> multiple sessions in one file and a concise identification of the endpoint
> All Endpoints are producers as well a consumers, thus matching the
> asynchronous, bidirectional nature of a FIX session. Whether a session
> initiates a connetions or waits for one is configured in the quickfix config
> file.
> All quickfix features (message store persistence, logging, threading model,
> JMX support, config file) can be configured through dependency injection, see
> the class QuickfixConfig.java and the quickfix config quide.
> The example PassiveFixGateway demonstrates a simple FIX relay, routing
> messages between two FIX sessions in both directions. To run it, build the
> component, cd into traget/test-classes and run it. FIX Messages sent to one
> endpoint will appear on the other.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
