Hello Bengt, I've started working with Hadrian to contribute updates to the QuickFIX/J component. After reading this thread, I've added the ability to export the QFJ JMX MBeans.
The new component addresses some of the issues you've raised in JIRA. The component will infer which log and message store implementations to use based on the QFJ settings. It will also provide all FIX session events including admin and application messages and session creation, logon and logoff events. The session event category is inserted in the exchange headers and can be used for routing, filtering or other purposes. I'll look into the issues with exception handling and modifying outgoing admin messages like the Logon message (for adding user ID and passwords, etc.). There's a similar issue with intercepting outgoing application messages during a resend operation. As you probably know, the FIX app has the ability to "veto" the resend of specific messages. I'll need to discuss these features with the Camel developers to determine the best way to implement them using an idiomatic Camel approach. Hopefully, we'll have some more details soon. Regards, Steve On 9/15/10 2:37 AM, "Bengt Rodehav" <be...@rodehav.com> wrote: > QuickFix/J supports JMX but the earlier incarnations of the Camel / QuickFix > integration did not. That's one of the reasons I couldn't use the Camel > component for QuickFix/J at the time but rolled my own instead. I made some > comments about this at the end of the following JIRA: > > https://issues.apache.org/activemq/browse/CAMEL-1350 > > We never made it to production at that point (due to non-technical reasons) > which is why I haven't re-iterated this subject. Perhaps some of my findings > have been fixed and some were invalid. I think Charles Moulliard is the best > man to answer those questions. > > I've been meaning to contribute in this area but haven't had the time yet. I > was hoping that Steve Bate (founder of QuickFix/J) was getting involved but > it doesn't seem to happen. > > Charles do you have any comments on the current status of the camel-quickfix > component - especially with regards to the issues I found some time back? > > /Bengt > <https://issues.apache.org/activemq/browse/CAMEL-1350> > > 2010/9/15 Claus Ibsen <claus.ib...@gmail.com> > >> To my knowledge the camel-quickfix component doesnt offer JMX management. >> Maybe QuickFix itself has some JMX management, you can tap into. >> >> Otherwise we love contributions and you are welcome to work on adding >> JMX management for camel-quickfix. >> >> See for example how you can annotate the endpoint >> >> https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apa >> che/camel/component/timer/TimerEndpoint.java >> >> You can do the same for the Producer / Consumer etc. >> Just implement the ManagementAware interface. >> >> There may be more details here as well >> http://camel.apache.org/camel-jmx.html >> >> >> >> On Wed, Sep 15, 2010 at 6:35 AM, vcheruvu <v_cher...@hotmail.com> wrote: >>> >>> Hi, >>> >>> I have started Camel-QuickFix component as an acceptor. I have managed to >>> send mock fix messages to the my Camel-Quickfix from FIX Simulator. Now I >> am >>> trying to turn on JMX support for Camel-QuickFIX component. I went >> through >>> the QuickFixAcceptor code and have not seen any code that enable JMX >>> support for QuickFix. How can I enable JMX support for Quickfix in Camel >> so >>> that i could invoke reset, logon, logout and disconnect operations? >>> >>> >>> Kind regards, >>> -Vid- >>> >>> -- >>> View this message in context: >> http://camel.465427.n5.nabble.com/Camel-QuickFIX-JMX-console-to-invoke-quickf >> ix-server-operations-tp2840088p2840088.html >>> Sent from the Camel - Users mailing list archive at Nabble.com. >>> >> >> >> >> -- >> Claus Ibsen >> Apache Camel Committer >> >> Author of Camel in Action: http://www.manning.com/ibsen/ >> Open Source Integration: http://fusesource.com >> Blog: http://davsclaus.blogspot.com/ >> Twitter: http://twitter.com/davsclaus >>
