QFJ-888: DefaultMessageFactory does not support FIX5.0 SP1/2 #171
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The background for this change is described in QFJ-888.
Changes are as follows:
MessageFactory
which accepts anApplVerID
. The default behavior of the new method is to callMessageFactory.create(beginString, msgType)
in order to maintain backwards compatibility.MessageUtils.parse
to call the new create method, passing in theApplVerID
acquired from the incoming message or the session. Other calls toMessageFactory.create
have remained as-is.DefaultMessageFactory
which accepts anApplVerID
value to be used as the default whencreate(beginString, msgType)
orcreate(beginString, null, msgType)
is called. The existing constructor calls the new one, passing inApplVerID.FIX50
in order to maintain backwards compatibility.DefaultMessageFactory
has been moved to the new create method. The old create method callscreate(beginString, null, msgType)
. In the case whereapplVerID
is null, thedefaultApplVerID
is used instead.Ultimately, these changes provide the following:
DefaultMessageFactory
can now specify a defaultApplVerID
to be used for FIXT message construction.ApplVerID
in the incoming message/session.