Axon 2.3.1 has been released. It contains fixes for a small number of issues found in 2.3.

2.3.1 comes with a fix that solves timing issues in transaction commits in the JdbcEventStore when the transaction was started outside the scope of the unit of work. In that case, the transaction was committed, regardless of any Spring Transaction Manager being present to manage it. Although it’s not likely to affect you, it may have some unwanted side effects in case errors occur. That’s why we recommend upgrading.

We have also fixed an issue in the Given When Then fixtures for Sagas, where the validation of dispatched commands would throw a NullPointerException when a field has an unexpected null value. This didn’t cause any false positives, nor false negatives. It’s just an fix of the error message that is reported.

There is a new module: axon-springmessaging. It is the new version of the axon-integration module that supports Spring 4’s Messaging API. So, if you’re on Spring 4, you should use the axon-springmessaging module instead.

There as a limitation that Spring beans couldn’t be used as @EventHandler or @EventSourcingHandler parameters on aggregate roots and entities. 2.3.1 comes with a fix that removes this limitation. You’re now free to use the same parameters types on these methods as any other @EventHandler or @CommandHandler method out there.