Deprecated API
Contents
-
Terminally Deprecated ElementsElementDescriptionResponses are sent in a non-blocking fashion and don't need a dedicated thread pool anymoreResponses are sent in a non-blocking fashion and don't need a dedicated thread pool anymoreas this method purely exists for interoperability between Axon Framework 4 and Axon Framework 5Temporary bridge for reading Axon Framework 4 multi-source token stores after upgrading. Scheduled for removal in 5.5.0, once existing stores have migrated to the Axon Framework 5 token class names.in favor of
EntityNotFoundException, which more broadly serves anyRepositorybeing unable to find or> recreate an entityuseSourcingCondition.strategy()'s and check for theabsolute modeUseClockUtils.set(Clock)if you have to provide a non-defaultClockinstance.in favor ofHandlerExecutionException.getDetails(Class), or any of theType,TypeReference, orConverterparameter combinations, as those ensure the details are converted to the desired typeUseEventHandlingComponentsConfigurer.ComponentsPhase.autodetected(String, ComponentBuilder)to provide an explicit component name. When no name is provided, the component receives its registration index as the name. Note that the generated index may differ across environments or application restarts, so it should not be relied upon for stable identification (e.g., in dead letter queues).UseEventHandlingComponentsConfigurer.ComponentsPhase.declarative(String, ComponentBuilder)to provide an explicit component name. When no name is provided, the component receives its registration index as the name. Note that the generated index may differ across environments or application restarts, so it should not be relied upon for stable identification (e.g., in dead letter queues).UseClockUtils.set(Clock)if you have to provide a non-defaultClockinstance.UseClockUtils.set(Clock)if you have to provide a non-defaultClockinstance.Temporary bridge for reading Axon Framework 4 token stores after upgrading. Scheduled for removal in 5.5.0, once existing stores have migrated to the Axon Framework 5 token class names.Temporary bridge for reading Axon Framework 4 token stores after upgrading. Scheduled for removal in 5.5.0, once existing stores have migrated to the Axon Framework 5 token class names.in favor ofSubscribingEventProcessor.processAsync(List, ProcessingContext), which reports completion and failures through the returnedCompletableFuturerather than blocking the calling thread. This method is retained for backward compatibility and blocks until processing finishes.UseAxonTestPhase.Then.Command.resultMessagePayloadSatisfies(Class, Consumer)instead, which automatically handles payload conversion for distributed setups where conversion is necessary.
-
Deprecated InterfacesInterfaceDescriptionTemporary bridge for reading Axon Framework 4 token stores after upgrading. Scheduled for removal in 5.5.0, once existing stores have migrated to the Axon Framework 5 token class names.
-
Deprecated ClassesClassDescriptionTemporary bridge for reading Axon Framework 4 multi-source token stores after upgrading. Scheduled for removal in 5.5.0, once existing stores have migrated to the Axon Framework 5 token class names.Only in use for legacy "sync" components.Temporary bridge for reading Axon Framework 4 token stores after upgrading. Scheduled for removal in 5.5.0, once existing stores have migrated to the Axon Framework 5 token class names.Coupling the id resolver directly to the
AnnotatedEntityMetamodelprevents theEntityMetamodelfrom being decorated or replaced, since resolution would break whenever the registered component is not anAnnotatedEntityMetamodel. Payload conversion to the handler's expected representation is now applied independently of the metamodel component, so annotation-based resolution only needs the plainAnnotationBasedEntityIdResolver. No direct replacement is required.Performing the payload conversion inside the resolver ties it to theAnnotatedEntityMetamodel, which prevents theEntityMetamodelcomponent from being decorated or replaced. Payload conversion is now applied independently of the metamodel component, so annotation-based id resolution only needs the plainAnnotationBasedEntityIdResolverDefinition. This definition remains functional for existing configurations but requires the resolvedEntityMetamodelto be anAnnotatedEntityMetamodel.
-
Deprecated Exception ClassesException ClassDescriptionin favor of
EntityNotFoundException, which more broadly serves anyRepositorybeing unable to find or> recreate an entity
-
Deprecated MethodsMethodDescriptionResponses are sent in a non-blocking fashion and don't need a dedicated thread pool anymoreResponses are sent in a non-blocking fashion and don't need a dedicated thread pool anymoreas this method purely exists for interoperability between Axon Framework 4 and Axon Framework 5use
SourcingCondition.strategy()'s and check for theabsolute modeIn favor of using the constructor, as we intend to enforce thinking about thetype.in favor ofHandlerExecutionException.getDetails(Class), or any of theType,TypeReference, orConverterparameter combinations, as those ensure the details are converted to the desired typeUseEventHandlingComponentsConfigurer.ComponentsPhase.autodetected(String, ComponentBuilder)to provide an explicit component name. When no name is provided, the component receives its registration index as the name. Note that the generated index may differ across environments or application restarts, so it should not be relied upon for stable identification (e.g., in dead letter queues).UseEventHandlingComponentsConfigurer.ComponentsPhase.declarative(String, ComponentBuilder)to provide an explicit component name. When no name is provided, the component receives its registration index as the name. Note that the generated index may differ across environments or application restarts, so it should not be relied upon for stable identification (e.g., in dead letter queues).UseClockUtils.set(Clock)if you have to provide a non-defaultClockinstance.UseClockUtils.set(Clock)if you have to provide a non-defaultClockinstance.in favor ofSubscribingEventProcessor.processAsync(List, ProcessingContext), which reports completion and failures through the returnedCompletableFuturerather than blocking the calling thread. This method is retained for backward compatibility and blocks until processing finishes.UseAxonTestPhase.Then.Command.resultMessagePayloadSatisfies(Class, Consumer)instead, which automatically handles payload conversion for distributed setups where conversion is necessary.
-
Deprecated ConstructorsConstructorDescriptionUse
ClockUtils.set(Clock)if you have to provide a non-defaultClockinstance.in favor of theAnnotationSpecification(Class, String, Class, String, Class, String)constructor that allows annotation configuration per resolvable attribute