Re: [Quickfix-users] How can I EOD with quickfix/j initiator

[Chris v. O. <chr...@gn...>]

On Fri, 2006-02-17 at 09:29 -0600, Dale Wilson wrote:

> The answer to your question depends on what you are trying to do.

  In a nutshell, I have a swing app (a highly altered Banzai) that I use
to test our in-house, proprietary FIX handlers. This is just a tool I am
using that I need to be able to quickly create and execute test
scenarios. The developer is generally debugging the legacy code in
Eclipse, and Im running also out of Eclipse.... it is frequent that we
need to quickly come up with a "clean" session after he makes a code
change. Currently, depending on if the session is so borked that we need
to EOD, I have to quit my app, find the store directory in Eclipse, ask
Eclipse to "refresh", then delete the store and seq numbers, then
restart my app.

  It would be convenient if I could prompt a disconnect, then have an
option to EOD from my GUI, then restart. Im sure I could parse the store
location from the application config file and clobber the files myself,
but I just figured that there was a method already in place to do that.
It sounds like there isnt, or Im just not being clear enough about what
Im trying to do.

> If you are stopping and restarting the application the cleanest solution 
> may be to "manually" reset the sequence number files in the store 
> directory -- probably in a script file you use to start the app.

  Unfortunately there are too many variables to do it this way, and it
still wouldnt be *as* convenient.

> Another approach would be to put code in the onCreate callback to 
> conditionally reset the expected sequence number(s) in the newly created 
> Session before you actually start the initiator or acceptor.

  How would I do this? And would simply resetting the sequence numbers
have the desired effect of ignoring any previous data in the message
store?

>   You 
> probably don't want this code to escape into the production version.

  Luckily for mankind, it wont.... this is just a tool completely
separate from any production code.

> If you're trying to do this while keeping the applicaiton up and running 
> then it's a more difficult proposition.   If this is the case, provide 
> more information about what you would like to happen (and maybe why (grin))

  Its merely a convenience for me ... but I just imagined that there
would be a method for this for the sake of developers and systems guys.

Thanks for your help,
Chris