Deprecated List (Axon Framework 4.6.8 API)

Deprecated Interfaces
Interface and Description
org.axonframework.modelling.command.inspection.CommandHandlerInterceptorHandlingMember in favor of the more generic `MessageInterceptingMember`
org.axonframework.axonserver.connector.heartbeat.ConnectionSanityChecker in through use of the AxonServer java connector
org.axonframework.axonserver.connector.heartbeat.HeartbeatSource in through use of the AxonServer java connector
org.axonframework.axonserver.connector.InstructionResultPublisher in through use of the AxonServer java connector
org.axonframework.axonserver.connector.Publisher in through use of the AxonServer java connector

Deprecated Classes
Class and Description
org.axonframework.spring.config.AbstractAnnotationHandlerBeanPostProcessor Replaced by the `MessageHandlerLookup` and `MessageHandlerConfigurer`, eliminating the need of an abstract implementation used for command and query registration.
org.axonframework.axonserver.connector.heartbeat.connection.checker.ActiveGrpcChannelChecker in through use of the AxonServer java connector
org.axonframework.commandhandling.model.AggregateScopeDescriptor in favor of the `AggregateScopeDescriptor`
org.axonframework.spring.config.annotation.AnnotationCommandHandlerBeanPostProcessor Replaced by the `MessageHandlerLookup` and `MessageHandlerConfigurer`.
org.axonframework.spring.config.AnnotationDrivenRegistrar Use Spring Boot autoconfiguration or register the individual beans explicitly. `AnnotationDriven` contains a list of look-up and registration components to replace this component with.
org.axonframework.spring.config.annotation.AnnotationQueryHandlerBeanPostProcessor Replaced by the `MessageHandlerLookup` and `MessageHandlerConfigurer`.
org.axonframework.spring.config.ApplicationContextLookupParameterResolverFactory Use Spring Boot autoconfiguration or register the individual beans explicitly.
org.axonframework.test.utils.AutowiredResourceInjector in favor of the `SimpleResourceInjector`
org.axonframework.spring.config.AxonConfiguration Replaced by the `SpringConfigurer` and `SpringAxonConfiguration`.
org.axonframework.spring.config.CommandHandlerSubscriber Replaced by the `MessageHandlerLookup` and `MessageHandlerConfigurer`.
org.axonframework.spring.config.ConfigurerFactoryBean Replaced by the `SpringConfigurer`, which itself is a `Configurer` implementation.
org.axonframework.axonserver.connector.util.ContextAddingInterceptor in through use of the AxonServer java connector
org.axonframework.axonserver.connector.DefaultHandlers in through use of the AxonServer java connector
org.axonframework.axonserver.connector.query.subscription.DeserializedResult in through use of the AxonServer java connector
org.axonframework.axonserver.connector.query.subscription.DisposableResult in through use of the AxonServer java connector
org.axonframework.axonserver.connector.event.util.EventCipher in through use of the AxonServer java connector
org.axonframework.spring.config.EventHandlerRegistrar Replaced by the `MessageHandlerLookup` and `MessageHandlerConfigurer`.
org.axonframework.axonserver.connector.util.FlowControllingStreamObserver in through use of the AxonServer java connector
org.axonframework.eventsourcing.eventstore.GapAwareTrackingToken in favor of the `GapAwareTrackingToken`
org.axonframework.domain.GenericEventMessage this class is available for backward compatibility with instances that were serialized with Axon 2. Use `GenericEventMessage` instead.
org.axonframework.domain.GenericMessage this class is available for backward compatibility with instances that were serialized with Axon 2. Use `GenericMessage` instead.
org.axonframework.eventsourcing.eventstore.GlobalSequenceTrackingToken in favor of the `GlobalSequenceTrackingToken`
org.axonframework.axonserver.connector.util.GrpcBufferingInterceptor in through use of the AxonServer java connector
org.axonframework.axonserver.connector.heartbeat.source.GrpcHeartbeatSource in through use of the AxonServer java connector
org.axonframework.axonserver.connector.heartbeat.HeartbeatConfiguration in through use of the AxonServer java connector
org.axonframework.axonserver.connector.heartbeat.connection.checker.HeartbeatConnectionChecker in through use of the AxonServer java connector
org.axonframework.axonserver.connector.heartbeat.HeartbeatMonitor in through use of the AxonServer java connector
org.axonframework.serialization.JavaSerializer in favor of the `XStreamSerializer` and `JacksonSerializer`, as direct Java serialization is relatively error prone. We hence strongly encourage to use either the XStream or Jackson solution in favor of this `Serializer` implementation.
org.axonframework.domain.MetaData this class is available for backward compatibility with instances that were serialized with Axon 2. Use `MetaData` instead.
org.axonframework.mongo.eventsourcing.eventstore.MongoTrackingToken this class is available for backward compatibility with instances that were serialized with Axon 3. Use `org.axonframework.extensions.mongo.eventsourcing.eventstore.MongoTrackingToken` instead.
org.axonframework.eventsourcing.MultiStreamableMessageSource In favor of `MultiStreamableMessageSource`. This class belongs in the `messaging` module instead of the `eventsourcing` module.
org.axonframework.eventsourcing.MultiStreamableMessageSource.Builder In favor of `MultiStreamableMessageSource.Builder`. This class belongs in the `messaging` module instead of the `eventsourcing` module.
org.axonframework.micrometer.PayloadTypeMessageMonitorWrapper As of release 4.4, replaced by using `Tag`s on the monitor implementations. Use {@link org.axonframework.micrometer.GlobalMetricRegistry#registerWithConfigurerWithDefaultTags(Configurer) to achieve the same behavior as this implementation.
org.axonframework.spring.config.QueryHandlerSubscriber Replaced by the `MessageHandlerLookup` and `MessageHandlerConfigurer`.
org.axonframework.spring.config.RepositoryFactoryBean Replaced by the `SpringAggregateLookup` and `SpringAggregateConfigurer`.
org.axonframework.axonserver.connector.util.ResubscribableStreamObserver in through use of the AxonServer java connector
org.axonframework.eventhandling.saga.SagaScopeDescriptor in favor of the `SagaScopeDescriptor`
org.axonframework.spring.config.SpringAxonAutoConfigurer Replaced by the `SpringConfigurer` and `SpringAxonConfiguration`.
org.axonframework.spring.config.annotation.SpringContextHandlerDefinitionBuilder Replaced by the `HandlerDefinitionFactoryBean`.
org.axonframework.spring.config.annotation.SpringContextParameterResolverFactoryBuilder Use Spring Boot autoconfiguration or register the individual beans explicitly.
org.axonframework.spring.config.annotation.SpringHandlerDefinitionBean Replaced by the `HandlerDefinitionFactoryBean`.
org.axonframework.spring.config.annotation.SpringHandlerEnhancerDefinitionBean Replaced by the `HandlerDefinitionFactoryBean`.
org.axonframework.test.aggregate.StubAggregateLifecycleRule in favor of `StubAggregateLifecycleExtension` to be used in combination with Junit 5
org.axonframework.queryhandling.SubscriptionQueryBackpressure since 3.4.0 Reactor version, Sinks API does not use FluxSink.OverflowStrategy
org.axonframework.axonserver.connector.util.TokenAddingInterceptor in through use of the AxonServer java connector
org.axonframework.spring.config.TransactionManagerFactoryBean Use Spring Boot autoconfiguration or register the individual beans explicitly.

Deprecated Exceptions
Exceptions and Description

org.axonframework.axonserver.connector.event.util.EventStoreClientException
in through use of the AxonServer java connector

Deprecated Exceptions
Exceptions and Description
org.axonframework.axonserver.connector.event.util.EventStoreClientException in through use of the AxonServer java connector

Deprecated Annotation Types
Annotation Type and Description
org.axonframework.spring.config.AnnotationDriven Use Spring Boot autoconfiguration or register the individual beans explicitly. Check the "See also" list for which individual beans to register.
org.axonframework.spring.config.NoBeanOfType Use Spring Boot autoconfiguration or register the individual beans explicitly. Check the "See also" list for which individual beans to register.

Deprecated Fields
Field and Description
org.axonframework.eventhandling.scheduling.quartz.QuartzEventScheduler.DirectEventJobDataBinder.EVENT_KEY in favor of the default message keys \| only maintained for backwards compatibility
org.axonframework.deadline.quartz.DeadlineJob.DeadlineJobDataBinder.SERIALIZED_DEADLINE_MESSAGE in favor of the separate DeadlineMessage keys \| only maintained for backwards compatibility
org.axonframework.deadline.quartz.DeadlineJob.DeadlineJobDataBinder.SERIALIZED_DEADLINE_MESSAGE_CLASS_NAME in favor of the separate DeadlineMessage keys \| only maintained for backwards compatibility

Deprecated Methods
Method and Description
org.axonframework.test.aggregate.TestExecutor.andThenTimeAdvancesTo(Instant) in favor of `TestExecutor.whenTimeAdvancesTo(Instant)`. This function incorrectly suggests you can proceed with other operations after calling it, which is made impossible due to the `ResultValidator` return type
org.axonframework.test.aggregate.TestExecutor.andThenTimeElapses(Duration) in favor of `TestExecutor.whenTimeElapses(Duration)`. This function incorrectly suggests you can proceed with other operations after calling it, which is made impossible due to the `ResultValidator` return type
org.axonframework.eventhandling.TrackingEventProcessorConfiguration.andWorkerTerminationTimeout(long) Use `TrackingEventProcessorConfiguration.andWorkerTerminationTimeout(long, TimeUnit)` instead.
org.axonframework.messaging.annotation.MessageHandlingMember.annotationAttributes(Class<? extends Annotation>) in favor of `MessageHandlingMember.attribute(String)`
org.axonframework.deadline.GenericDeadlineMessage.asDeadlineMessage(String, Object) Use `GenericDeadlineMessage.asDeadlineMessage(String, Object, Instant)` instead, as it sets the timestamp of the deadline, rather than the current time
org.axonframework.eventhandling.EventUtils.asDomainEventMessage(EventMessage<T>) since this method is not used for external use. This method is intended to deduce whether a given `EventMessage` is a `DomainEventMessage` and if not, push it into being one by adjusting the fields. However, this is only intended to simplify the storage of events. This does not make a regular `EventMessage` a `DomainEventMessage` by any means. The only way to have a true `DomainEventMessage` is by publishing events from within an Aggregate, by using the `AggregateLifecycle` operations.
org.axonframework.test.deadline.DeadlineManagerValidator.assertDeadlinesMet(Object...) in favor of `DeadlineManagerValidator.assertTriggeredDeadlines(Object...)`
org.axonframework.test.deadline.DeadlineManagerValidator.assertDeadlinesMetMatching(Matcher<? extends Iterable<?>>) in favor of `DeadlineManagerValidator.assertTriggeredDeadlinesMatching(Matcher)`
org.axonframework.axonserver.connector.AxonServerConnectionManager.Builder.axonFrameworkVersionResolver(Supplier<String>) Not ued anymore
org.axonframework.eventsourcing.MultiStreamableMessageSource.builder() In favor of `MultiStreamableMessageSource.builder()`. This class belongs in the `messaging` module instead of the `eventsourcing` module.
org.axonframework.micrometer.MessageTimerMonitor.buildMonitor(String, MeterRegistry) in favor of using the `MessageTimerMonitor.builder()`
org.axonframework.micrometer.EventProcessorLatencyMonitor.buildMonitor(String, MeterRegistry) in favor of using the `EventProcessorLatencyMonitor.builder()`
org.axonframework.micrometer.MessageTimerMonitor.buildMonitor(String, MeterRegistry, Clock) in favor of using the `MessageTimerMonitor.builder()`
org.axonframework.micrometer.MessageTimerMonitor.buildMonitor(String, MeterRegistry, Clock, Function<Message<?>, Iterable<Tag>>) in favor of using the `MessageTimerMonitor.builder()`
org.axonframework.micrometer.MessageTimerMonitor.buildMonitor(String, MeterRegistry, Function<Message<?>, Iterable<Tag>>) in favor of using the `MessageTimerMonitor.builder()`
org.axonframework.micrometer.EventProcessorLatencyMonitor.buildMonitor(String, MeterRegistry, Function<Message<?>, Iterable<Tag>>) in favor of using the `EventProcessorLatencyMonitor.builder()`
org.axonframework.commandhandling.distributed.CommandCallbackRepository.cancelCallbacks(A) use `CommandCallbackRepository.cancelCallbacksForChannel(Object)` instead
org.axonframework.modelling.command.inspection.EntityModel.commandHandlerInterceptors() use `EntityModel.allCommandHandlerInterceptors()` or `EntityModel.commandHandlerInterceptors(Class)` instead
org.axonframework.modelling.command.inspection.EntityModel.commandHandlers() use `EntityModel.allCommandHandlers()` or `EntityModel.commandHandlers(Class)` instead
org.axonframework.serialization.xml.XStreamSerializer.defaultSerializer() in favor of using the `XStreamSerializer.builder()` to construct an instance using a configured `XStream` instance. Using this shorthand still works, but will use an `XStream` instance that allows everything. Although this works, XStream expects the types or wildcards for the types to be defined to ensure the application stays secure. As such, it is highly recommended to follow their recommended approach.
org.axonframework.eventsourcing.eventstore.jdbc.JdbcEventStorageEngine.domainEventFields() in favor of `EventSchema.domainEventFields()`
org.axonframework.test.matchers.Matchers.equalTo(T) Please use the `Matchers.deepEquals(Object)` instead. Using this method will lead to unwanted exceptions when ran on JDK 17 and up, due to adjustments in reflective access.
org.axonframework.test.matchers.Matchers.equalTo(T, FieldFilter) Please use the `Matchers.deepEquals(Object, FieldFilter)` instead. Using this method will lead to unwanted exceptions when ran on JDK 17 and up, due to adjustments in reflective access.
org.axonframework.test.aggregate.ResultValidator.expectDeadlinesMet(Object...) in favor of `ResultValidator.expectTriggeredDeadlines(Object...)`
org.axonframework.test.saga.FixtureExecutionResult.expectDeadlinesMet(Object...) in favor of `FixtureExecutionResult.expectTriggeredDeadlines(Object...)`
org.axonframework.test.aggregate.ResultValidator.expectDeadlinesMetMatching(Matcher<? extends List<? super DeadlineMessage<?>>>) in favor of `ResultValidator.expectTriggeredDeadlinesMatching(Matcher)`
org.axonframework.test.saga.FixtureExecutionResult.expectDeadlinesMetMatching(Matcher<? extends List<? super DeadlineMessage<?>>>) in favor of `FixtureExecutionResult.expectTriggeredDeadlinesMatching(Matcher)`
org.axonframework.axonserver.connector.AxonServerConnectionManager.getChannel()
org.axonframework.axonserver.connector.AxonServerConnectionManager.getChannel(String)
org.axonframework.test.deadline.StubDeadlineManager.getDeadlinesMet() in favor of `StubDeadlineManager.getTriggeredDeadlines()`
org.axonframework.messaging.annotation.AnnotatedHandlerInspector.getHandlers() use `AnnotatedHandlerInspector.getAllHandlers()` or `AnnotatedHandlerInspector.getHandlers(Class)` instead
org.axonframework.messaging.annotation.MessageHandlingMember.hasAnnotation(Class<? extends Annotation>) in favor of `MessageHandlingMember.attribute(String)`
org.axonframework.messaging.annotation.InterceptorChainParameterResolverFactory.initialize(InterceptorChain) in favor of `InterceptorChainParameterResolverFactory.callWithInterceptorChain(InterceptorChain, Callable)`
org.axonframework.axonserver.connector.query.AxonServerQueryBus.Builder.instructionAckSource(InstructionAckSource<QueryProviderOutbound>) in through use of the AxonServer java connector
org.axonframework.modelling.command.inspection.AbstractChildEntityDefinition.isFieldTypeSupported(Field) in favour of `AbstractChildEntityDefinition.isMemberTypeSupported(Member)`
org.axonframework.eventhandling.tokenstore.jdbc.TokenSchema.ownerColum() in favor of `TokenSchema.ownerColumn`
org.axonframework.config.ModuleConfiguration.phase() a `ModuleConfiguration`'s phase is no longer used, as distinct phases might be necessary for any of the start or shutdown processes added in the `ModuleConfiguration.initialize(Configuration)` method
org.axonframework.config.Configurer.registerCommandHandler(int, Function<Configuration, Object>) in favor of `Configurer.registerCommandHandler(Function)`, since the `phase` of an annotated handler should be defined through the `StartHandler`/`ShutdownHandler` annotation.
org.axonframework.config.Configurer.registerQueryHandler(int, Function<Configuration, Object>) in favor of `Configurer.registerQueryHandler(Function)`, since the `phase` of an annotated handler should be defined through the `StartHandler`/`ShutdownHandler` annotation.
org.axonframework.queryhandling.SimpleQueryUpdateEmitter.registerUpdateHandler(SubscriptionQueryMessage<?, ?, ?>, SubscriptionQueryBackpressure, int) in favour of using {`SimpleQueryUpdateEmitter.registerUpdateHandler(SubscriptionQueryMessage, int)`}
org.axonframework.queryhandling.QueryUpdateEmitter.registerUpdateHandler(SubscriptionQueryMessage<?, ?, ?>, SubscriptionQueryBackpressure, int) in favour of using {`QueryUpdateEmitter.registerUpdateHandler(SubscriptionQueryMessage, int)`}
org.axonframework.axonserver.connector.query.AxonServerQueryBus.Builder.requestStreamFactory(Function<UpstreamAwareStreamObserver<QueryProviderInbound>, StreamObserver<QueryProviderOutbound>>) in through use of the AxonServer java connector
org.axonframework.axonserver.connector.query.subscription.SubscriptionMessageSerializer.serialize(SubscriptionQueryMessage<?, ?, ?>) in through use of the AxonServer java connector
org.axonframework.eventsourcing.eventstore.jdbc.JdbcEventStorageEngine.setGapCleaningThreshold(int) Use the `gapCleaningThreshold(int)` in the `JdbcEventStorageEngine.builder()` instead
org.axonframework.eventsourcing.eventstore.jdbc.JdbcEventStorageEngine.setGapTimeout(int) Use the `gapTimeout(int)` in the `JdbcEventStorageEngine.builder()` instead
org.axonframework.eventhandling.tokenstore.jdbc.TokenSchema.Builder.setOwnerColum(String) in favor of `TokenSchema.Builder.setOwnerColumn(String)`
org.axonframework.config.ModuleConfiguration.shutdown() in favor of maintaining shutdown operations in the `Component`. Any lifecycle operations not covered through the components created by this `ModuleConfiguration` should be added to the `Configuration` in `ModuleConfiguration.initialize(Configuration)` through `LifecycleOperations.onShutdown(int, LifecycleHandler)`
org.axonframework.eventsourcing.eventstore.BatchingEventStorageEngine.Builder.snapshotFilter(Predicate<? super DomainEventData<?>>) in favor of `BatchingEventStorageEngine.Builder.snapshotFilter(SnapshotFilter)`
org.axonframework.eventsourcing.eventstore.AbstractEventStorageEngine.Builder.snapshotFilter(Predicate<? super DomainEventData<?>>) in favor of `AbstractEventStorageEngine.Builder.snapshotFilter(SnapshotFilter)`
org.axonframework.eventsourcing.eventstore.jpa.JpaEventStorageEngine.Builder.snapshotFilter(Predicate<? super DomainEventData<?>>) in favor of `JpaEventStorageEngine.Builder.snapshotFilter(SnapshotFilter)`
org.axonframework.eventsourcing.eventstore.jdbc.JdbcEventStorageEngine.Builder.snapshotFilter(Predicate<? super DomainEventData<?>>) in favor of `JdbcEventStorageEngine.Builder.snapshotFilter(SnapshotFilter)`
org.axonframework.axonserver.connector.event.axon.AxonServerEventStore.Builder.snapshotFilter(Predicate<? super DomainEventData<?>>) in favor of `AxonServerEventStore.Builder.snapshotFilter(SnapshotFilter)`
org.axonframework.config.ModuleConfiguration.start() in favor of maintaining start operations in the `Component`. Any lifecycle operations not covered through the components created by this `ModuleConfiguration` should be added to the `Configuration` in `ModuleConfiguration.initialize(Configuration)` through `LifecycleOperations.onStart(int, LifecycleHandler)`
org.axonframework.queryhandling.QueryGateway.subscriptionQuery(String, Q, ResponseType<I>, ResponseType<U>, SubscriptionQueryBackpressure) in favour of using {`QueryGateway.subscriptionQuery(String, Object, ResponseType, ResponseType)`}. To set a backpressure strategy, use one of the `onBackpressure..` operators on the updates flux directly. Example: `result.updates().onBackpressureBuffer(100)`
org.axonframework.queryhandling.QueryGateway.subscriptionQuery(String, Q, ResponseType<I>, ResponseType<U>, SubscriptionQueryBackpressure, int) in favour of using {`QueryGateway.subscriptionQuery(String, Object, ResponseType, ResponseType, int)`}. To set a backpressure strategy, use one of the `onBackpressure..` operators on the updates flux directly. Example: `result.updates().onBackpressureBuffer(100)`
org.axonframework.queryhandling.DefaultQueryGateway.subscriptionQuery(String, Q, ResponseType<I>, ResponseType<U>, SubscriptionQueryBackpressure, int) in favour of the {`DefaultQueryGateway.subscriptionQuery(String, Object, ResponseType, ResponseType, int)`}
org.axonframework.queryhandling.SimpleQueryBus.subscriptionQuery(SubscriptionQueryMessage<Q, I, U>, SubscriptionQueryBackpressure, int) in favor use of {`SimpleQueryBus.subscriptionQuery(SubscriptionQueryMessage, int)`
org.axonframework.queryhandling.QueryBus.subscriptionQuery(SubscriptionQueryMessage<Q, I, U>, SubscriptionQueryBackpressure, int) in favour of using {`QueryBus.subscriptionQuery(SubscriptionQueryMessage, int)`}
org.axonframework.axonserver.connector.query.AxonServerQueryBus.subscriptionQuery(SubscriptionQueryMessage<Q, I, U>, SubscriptionQueryBackpressure, int) in favor of using the {`AxonServerQueryBus.subscriptionQuery(SubscriptionQueryMessage, int)`}
org.axonframework.eventsourcing.eventstore.jdbc.JdbcEventStorageEngine.trackedEventFields() in favor of `EventSchema.trackedEventFields()`
org.axonframework.messaging.responsetypes.AbstractResponseType.unwrapIfTypeFuture(Type) Use `ReflectionUtils.unwrapIfType(Type, Class[])` instead
org.axonframework.test.aggregate.TestExecutor.whenThenTimeAdvancesTo(Instant) since 4.6. Use `TestExecutor.whenTimeAdvancesTo(Instant)` method
org.axonframework.test.aggregate.AggregateTestFixture.whenThenTimeAdvancesTo(Instant)
org.axonframework.test.aggregate.TestExecutor.whenThenTimeElapses(Duration) since 4.6. Use `TestExecutor.whenTimeAdvancesTo(Instant)` method
org.axonframework.test.aggregate.AggregateTestFixture.whenThenTimeElapses(Duration)
org.axonframework.eventhandling.pooled.PooledStreamingEventProcessor.Builder.workerExecutorService(ScheduledExecutorService) in favor of `PooledStreamingEventProcessor.Builder.workerExecutor(ScheduledExecutorService)`

Deprecated Constructors
Constructor and Description
org.axonframework.commandhandling.distributed.AbstractRoutingStrategy(UnresolvedRoutingKeyPolicy) in favor of `AbstractRoutingStrategy(RoutingStrategy)`
org.axonframework.modelling.command.AnnotationCommandTargetResolver() Please use the `AnnotationCommandTargetResolver.builder()`.
org.axonframework.commandhandling.distributed.AnnotationRoutingStrategy() in favor of the `AnnotationRoutingStrategy.builder()`
org.axonframework.commandhandling.distributed.AnnotationRoutingStrategy(Class<? extends Annotation>) in favor of the `AnnotationRoutingStrategy.builder()`
org.axonframework.commandhandling.distributed.AnnotationRoutingStrategy(Class<? extends Annotation>, UnresolvedRoutingKeyPolicy) in favor of the `AnnotationRoutingStrategy.builder()`
org.axonframework.commandhandling.distributed.AnnotationRoutingStrategy(UnresolvedRoutingKeyPolicy) in favor of the `AnnotationRoutingStrategy.builder()`
org.axonframework.axonserver.connector.query.subscription.AxonServerSubscriptionQueryResult(SubscriptionQueryResult, SubscriptionMessageSerializer) Deprecated in favor of constructor with a `SpanFactory`. This constructor defaults to a `NoOpSpanFactory`.
org.axonframework.eventhandling.scheduling.quartz.QuartzEventScheduler.DirectEventJobDataBinder() in favor of `DirectEventJobDataBinder(Serializer)`, as the `Serializer` is a hard requirement.
org.axonframework.commandhandling.callbacks.FailureLoggingCallback(CommandCallback<C, R>) Please use `CommandCallback.wrap(CommandCallback)` to wrap a command with a delegate and use the `FailureLoggingCallback(org.slf4j.Logger, org.axonframework.commandhandling.CommandCallback<C, R>)` to create this callback
org.axonframework.commandhandling.callbacks.FailureLoggingCallback(Logger, CommandCallback<C, R>) Please use `CommandCallback.wrap(CommandCallback)` to wrap a command with a delegate and use the `FailureLoggingCallback(Logger)` to specify you custom logger.
org.axonframework.metrics.MessageTimerMonitor() in favor of the `MessageTimerMonitor.builder()`
org.axonframework.metrics.MessageTimerMonitor(Clock) in favor of the `MessageTimerMonitor.builder()`
org.axonframework.commandhandling.distributed.MetaDataRoutingStrategy(String) in favor of the `MetaDataRoutingStrategy.builder()`
org.axonframework.commandhandling.distributed.MetaDataRoutingStrategy(String, UnresolvedRoutingKeyPolicy) in favor of the `MetaDataRoutingStrategy.builder()`
org.axonframework.eventsourcing.MultiStreamableMessageSource(MultiStreamableMessageSource.Builder) In favor of `MultiStreamableMessageSource(org.axonframework.eventhandling.MultiStreamableMessageSource.Builder)`. This class belongs in the `messaging` module instead of the `eventsourcing` module.
org.axonframework.eventhandling.ReplayToken(TrackingToken) Use the `ReplayToken.createReplayToken(TrackingToken)` method instead.
org.axonframework.eventhandling.ReplayToken(TrackingToken, TrackingToken) Use the `ReplayToken.createReplayToken(TrackingToken, TrackingToken)` method instead.
org.axonframework.eventsourcing.snapshotting.RevisionSnapshotFilter(String) in favor of using the `RevisionSnapshotFilter.Builder`
org.axonframework.modelling.command.VersionedAggregateIdentifier(String, Long) In favor of `VersionedAggregateIdentifier(Object, Long)`, since the `identifier` can be a non-`String`.

Deprecated Annotation Type Elements
Annotation Type Element and Description
org.axonframework.modelling.command.AggregateIdentifier.routingKey this field is no longer used to route commands to an aggregate. The aggregate to route a command to will be resolved with the `TargetAggregateIdentifier` annotated field in the `CommandMessage`'s payload itself.

Deprecated API

Contents