MessageCracker.Crack has no generic code path... about quickfixn HOT 3 CLOSED

You don't have to implement all OnMessage methods.

You only implement OnMessage for each message type you want to handle. If crack doesn't find the appropriate handler, it rejects the message. This is by design.

The engine is supposed to reject all message types that you don't handle. The implication is that you don't support that type, therefore they shouldn't be sending it to you in the first place. This is pretty standard FIX behavior.

I've never connected to a counterparty that supports all message types. I don't think there are any.

from quickfixn.

Well, the main problem is: Already in the initial connection there are messages I dont really want to handle, but I want to use cracker. Heartbeat for example is something I see but that is handled fully by the framework. Logon/Logoff is something I have at the moment no interest to manually handle. RIght now I need t ogo through everything. With a Try method I could implement those that I want, but then basically decide myself what to do with the others.

from quickfixn.

You don't have to handle any of that.

See the "EXAMPLE MESSAGE CRACKER" code on this page: http://quickfixn.org/tutorial/receiving-messages

Your code should look similar to that. See all those empty function callbacks? Those are perfectly okay.

Don't overthink the Cracker. You call crack() in FromApp, and it will dispatch to the OnMessage() handlers. If the OnMessage handler is not present, then the message is rejected. That's all there is to it.

FromApp (thus Cracker) is only for application-level messages. Logon, Logoff, Heartbeat, ResendRequest... etc are all admin messages, and thus don't apply; usually you don't want to mess with those anyway.

Have you looked at the example programs in the Examples directory?

(Our help docs are clearly not adequate. We will have to do better.)

from quickfixn.