Deprecated List (Axon Framework - Messaging 4.11.1 API)

Deprecated Interfaces
Interface and Description
org.axonframework.eventhandling.deadletter.legacyjpa.DeadLetterJpaConverter in favor of using `DeadLetterJpaConverter` which moved to jakarta.
org.axonframework.common.legacyjpa.EntityManagerProvider in favor of using `EntityManagerProvider` which moved to jakarta.

Deprecated Classes
Class and Description
org.axonframework.messaging.interceptors.legacyvalidation.BeanValidationInterceptor in favor of using `BeanValidationInterceptor` which moved to jakarta.
org.axonframework.common.caching.EhCacheAdapter since ehcache 2 is nearing eol, we added `EhCache3Adapter` instead, which uses ehcache 3.
org.axonframework.eventhandling.deadletter.legacyjpa.EventMessageDeadLetterJpaConverter in favor of using `EventMessageDeadLetterJpaConverter` which moved to jakarta.
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.eventhandling.deadletter.legacyjpa.JpaDeadLetter in favor of using `JpaDeadLetter` which moved to jakarta.
org.axonframework.eventhandling.deadletter.legacyjpa.JpaSequencedDeadLetterQueue in favor of using `JpaSequencedDeadLetterQueue` which moved to jakarta.
org.axonframework.eventhandling.tokenstore.legacyjpa.JpaTokenStore in favor of using `JpaTokenStore` which moved to jakarta.
org.axonframework.tracing.NestingSpanFactory Various components have dedicated tracing SpanFactory interfaces since 4.9.0. This includes the `CommandBus`, `EventProcessor` and `QueryBus`. Use the `distributedInSameTrace` of these instead.
org.axonframework.common.legacyjpa.PagingJpaQueryIterable in favor of using `PagingJpaQueryIterable` which moved to jakarta.
org.axonframework.common.legacyjpa.SimpleEntityManagerProvider in favor of using `SimpleEntityManagerProvider` which moved to jakarta.
org.axonframework.queryhandling.SubscriptionQueryBackpressure since 3.4.0 Reactor version, Sinks API does not use FluxSink.OverflowStrategy

Deprecated Exceptions
Exceptions and Description
org.axonframework.messaging.interceptors.legacyvalidation.JSR303ViolationException in favor of using `JSR303ViolationException` which moved to jakarta.

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.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.commandhandling.distributed.CommandCallbackRepository.cancelCallbacks(A) use `CommandCallbackRepository.cancelCallbacksForChannel(Object)` 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.deadline.jobrunr.JobRunrDeadlineManager.execute(String) Kept for backwards compatibility, use `JobRunrDeadlineManager.execute(String, String)` instead.
org.axonframework.messaging.annotation.AnnotatedHandlerInspector.getHandlers() use `AnnotatedHandlerInspector.getAllHandlers()` or `AnnotatedHandlerInspector.getHandlers(Class)` instead
org.axonframework.queryhandling.SubscriptionQueryResult.handle(Consumer<? super I>, Consumer<? super U>) Please use `SubscriptionQueryResult.handle(Consumer, Consumer, Consumer)` instead, to consciously deal with any exceptions with the `errorConsumer`.
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.eventhandling.tokenstore.jdbc.TokenSchema.ownerColum() in favor of `TokenSchema.ownerColumn`
org.axonframework.queryhandling.QueryUpdateEmitter.registerUpdateHandler(SubscriptionQueryMessage<?, ?, ?>, SubscriptionQueryBackpressure, int) in favour of using {`QueryUpdateEmitter.registerUpdateHandler(SubscriptionQueryMessage, int)`}
org.axonframework.queryhandling.SimpleQueryUpdateEmitter.registerUpdateHandler(SubscriptionQueryMessage<?, ?, ?>, SubscriptionQueryBackpressure, int) in favour of using {`SimpleQueryUpdateEmitter.registerUpdateHandler(SubscriptionQueryMessage, int)`}
org.axonframework.eventhandling.tokenstore.jdbc.TokenSchema.Builder.setOwnerColum(String) in favor of `TokenSchema.Builder.setOwnerColumn(String)`
org.axonframework.deadline.jobrunr.JobRunrDeadlineManager.Builder.spanFactory(SpanFactory) Use `JobRunrDeadlineManager.Builder.spanFactory(DeadlineManagerSpanFactory)` instead as it provides more configuration options.
org.axonframework.deadline.SimpleDeadlineManager.Builder.spanFactory(SpanFactory) Use `SimpleDeadlineManager.Builder.spanFactory(DeadlineManagerSpanFactory)` instead as it provides more configuration options.
org.axonframework.deadline.dbscheduler.DbSchedulerDeadlineManager.Builder.spanFactory(SpanFactory) Use `DbSchedulerDeadlineManager.Builder.spanFactory(DeadlineManagerSpanFactory)` instead as it provides more configuration options.
org.axonframework.deadline.quartz.QuartzDeadlineManager.Builder.spanFactory(SpanFactory) Use `QuartzDeadlineManager.Builder.spanFactory(DeadlineManagerSpanFactory)` which provides more configuration options.
org.axonframework.commandhandling.distributed.DistributedCommandBus.Builder.spanFactory(SpanFactory) Use `DistributedCommandBus.Builder.spanFactory(CommandBusSpanFactory)` instead as it provides more configurability.
org.axonframework.commandhandling.SimpleCommandBus.Builder.spanFactory(SpanFactory) Use `SimpleCommandBus.Builder.spanFactory(CommandBusSpanFactory)` instead as it provides more configurability.
org.axonframework.eventhandling.AbstractEventBus.Builder.spanFactory(SpanFactory) Please use `AbstractEventBus.Builder.spanFactory(EventBusSpanFactory)` which is more configurable
org.axonframework.eventhandling.AbstractEventProcessor.Builder.spanFactory(SpanFactory) Use {@link #spanFactory(EventProcessorSpanFactory) for more configuration options instead
org.axonframework.eventhandling.TrackingEventProcessor.Builder.spanFactory(SpanFactory)
org.axonframework.eventhandling.SubscribingEventProcessor.Builder.spanFactory(SpanFactory)
org.axonframework.eventhandling.pooled.PooledStreamingEventProcessor.Builder.spanFactory(SpanFactory)
org.axonframework.queryhandling.SimpleQueryBus.Builder.spanFactory(SpanFactory) Use `SimpleQueryBus.Builder.spanFactory(QueryBusSpanFactory)` instead as it provides more configurability.
org.axonframework.queryhandling.SimpleQueryUpdateEmitter.Builder.spanFactory(SpanFactory) Use `SimpleQueryUpdateEmitter.Builder.spanFactory(QueryUpdateEmitterSpanFactory)` instead as it provides more configurability.
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.DefaultQueryGateway.subscriptionQuery(String, Q, ResponseType<I>, ResponseType<U>, SubscriptionQueryBackpressure, int) in favour of the {`DefaultQueryGateway.subscriptionQuery(String, Object, ResponseType, ResponseType, int)`}
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.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.messaging.responsetypes.AbstractResponseType.unwrapIfTypeFuture(Type) Use `ReflectionUtils.unwrapIfType(Type, Class[])` instead
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.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.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.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.eventhandling.ReplayToken(TrackingToken) Use the `ReplayToken.createReplayToken(TrackingToken)` method instead.
org.axonframework.eventhandling.ReplayToken(TrackingToken, TrackingToken) Use the `ReplayToken.createReplayToken(TrackingToken, TrackingToken)` method instead.

Deprecated API

Contents