Major Releases
最后更新于
最后更新于
This page notes all enhancements and features that we have introduced to our major releases of the Axon Spring Cloud Extension.
There is one mentionable adjustment apart from a multitude of dependency updates.
The IgnoreListingDiscoveryMode, which ignores ServiceInstances that don't contain any command handling capabilities, now evicts the ignored entries after a configurable timeframe. This solution ensures instances that were ignored for a retryable reason will be reevaluated after (by default) one minute. You can check up on the solution for this in pull request .
For a full list of all the changes, please check the .
This release has seen a bunch of adjustments towards the Spring Cloud extension, which can be grouped into two categories. Firstly, the introduction of the CapabilityDiscoveryMode and secondly the automatic process added to this project:
Introduced GitHub Actions to build, test and push snapshots of the Spring Cloud Extension, as has been marked in pull request .
Dependabot was introduced, ensuring all versions will be as up-to-date as possible.
JUnit4 has been removed entirely, in favor of JUnit 5.
The CapabilityDiscoveryMode mode has been introduced through issue . This approach allows for more flexibility when it comes to defining how command routing information should be retrieved and shared.
For a full list of all the changes, please check the .
Issue implements the CommandBusConnector#localSegment. Axon Framework introduces this method in release 4.3 (and issue ) to ensure the usage of the DisruptorCommandBus's repository is followed when distributing the CommandBus.
We introduced a graceful start-up and shutdown solution in Axon Framework release 4.3 for all infrastructure components. Issue ensures the SpringHttpCommandBusConnector complies with this style too.
We split off the Spring Cloud logic from Axon Framework core into a dedicated repository. Next to that, it complies with Axon Framework's 4.0 release.
For a complete list of all changes, see page.
When using the implementation of Spring Cloud the SpringCloudCommandRouter would throw NullPointerExceptions. This occurs because Spring Cloud Kubernetes does not support the ServiceInstance's metadata field, which the SpringCloudCommandRouter relies on. pull request introduced a null check to ensure the null pointer would not be thrown again.
The SpringCloudCommandRouter failed to correctly connect to a Spring Cloud Discovery Service if the node did not contain any Command Handler methods. This undesired behaviour was marked by user "travikk" and made more lenient under .