I’d like to share that Axon Framework 4.5.1 has been released today.
Some of the adjustments we’ve done for 4.5.1 are the following:
-
Some internals have changed concerning command handling exceptions.
Within a single JVM, Axon Framework knows whether the exception is transient or not.
This piece of information allows theRetryScheduler
to retry a non-transient exception since those are retryable.
With the move towards distributed environments, the information whether an exception is transient was lost when we moved to the dedicatedCommandHandlingException
containing a details object.
Pull request #1742 reintroduces this functionality in this release. -
The new
RevisionSnapshotFilter
introduced in release 4.5 sneaked in a bug by not validating the aggregate type upon filtering.
Pull request #1771 describes and solves the problem by introducing the aggregate type to theRevisionSnapshotFilter
. -
By enabling the
CreationPolicy
for theDisruptorCommandBus
, a timing issue was introduced with handling events.
Contributor “junkdog” marked the problem in issue #1778, after which pull request #1792 solved it. -
Contributor “michaelbub” noted in issue #1786 that resetting a
StreamingEventProcessor
to a point in the future reacted differently when no token was stored yet.
This followed from the implementation of theReplayToken
, which wrongfully assumed that if the given ‘token at reset’ wasnull
, the start position should benull
too.
However, the start position might be the future, and hence it should be used in favor ofnull
.
This issue is addressed under this pull request.
For a detailed perspective on the release notes, please check this page.