Your guardian actor, which should be able to take a message of type com.sackfix.bootstrap.SystemErrorNeedsDevOpsMsg and basically shutdown eg the server port is already bound to.
The optional persisten store, and also a boolean indicating if the initial sequence numbers should be read in, or left at 1
A trait you have written which must be able to receive messages of type org.sackfix.session.BusinessFixMessage(sfSessionActor:ActorRef, sessionId:SfSessionId, message:SfMessage) It in turn can reply to the sfSessionActor by sending it a org.sackfix.session.FixMsgOut(msgBody: SfFixMessageBody)
A trait you have written which must be able to receive messages of type org.sackfix.session.BusinessFixMessage(sfSessionActor:ActorRef, sessionId:SfSessionId, message:SfMessage) It in turn can reply to the sfSessionActor by sending it a org.sackfix.session.FixMsgOut(msgBody: SfFixMessageBody)
Your guardian actor, which should be able to take a message of type com.sackfix.bootstrap.SystemErrorNeedsDevOpsMsg and basically shutdown eg the server port is already bound to.
The optional persisten store, and also a boolean indicating if the initial sequence numbers should be read in, or left at 1
Constructor
Your guardian actor, which should be able to take a message of type com.sackfix.bootstrap.SystemErrorNeedsDevOpsMsg and basically shutdown eg the server port is already bound to.
The optional persisten store, and also a boolean indicating if the initial sequence numbers should be read in, or left at 1
A trait you have written which must be able to receive messages of type org.sackfix.session.BusinessFixMessage(sfSessionActor:ActorRef, sessionId:SfSessionId, message:SfMessage) It in turn can reply to the sfSessionActor by sending it a org.sackfix.session.FixMsgOut(msgBody: SfFixMessageBody)