-
Deprecated Interfaces
-
Deprecated ClassesClassDescriptionsince ehcache 2 is nearing eol, we added
EhCache3Adapterinstead, which uses ehcache 3.in favor of usingPagingJpaQueryIterablewhich moved to jakarta.in favor of usingSimpleEntityManagerProviderwhich moved to jakarta.in favor of usingEventMessageDeadLetterJpaConverterwhich moved to jakarta.in favor of usingJpaDeadLetterwhich moved to jakarta.in favor of usingJpaSequencedDeadLetterQueuewhich moved to jakarta.in favor of usingJpaTokenStorewhich moved to jakarta.in favor of usingBeanValidationInterceptorwhich moved to jakarta.since 3.4.0 Reactor version, Sinks API does not use FluxSink.OverflowStrategyin favor of theXStreamSerializerandJacksonSerializer, as direct Java serialization is relatively error prone. We hence strongly encourage to use either the XStream or Jackson solution in favor of thisSerializerimplementation.Various components have dedicated tracing SpanFactory interfaces since 4.9.0. This includes theCommandBus,EventProcessorandQueryBus. Use thedistributedInSameTraceof these instead.
-
Deprecated Exceptions
-
Deprecated FieldsFieldDescriptionin favor of the separate DeadlineMessage keys | only maintained for backwards compatibilityin favor of the separate DeadlineMessage keys | only maintained for backwards compatibilityin favor of the default message keys | only maintained for backwards compatibility
-
Deprecated MethodsMethodDescriptionorg.axonframework.commandhandling.distributed.DistributedCommandBus.Builder.spanFactory
(SpanFactory) UseDistributedCommandBus.Builder.spanFactory(CommandBusSpanFactory)instead as it provides more configurability.UseSimpleCommandBus.Builder.spanFactory(CommandBusSpanFactory)instead as it provides more configurability.UseDbSchedulerDeadlineManager.Builder.spanFactory(DeadlineManagerSpanFactory)instead as it provides more configuration options.UseGenericDeadlineMessage.asDeadlineMessage(String, Object, Instant)instead, as it sets the timestamp of the deadline, rather than the current timeUseJobRunrDeadlineManager.Builder.spanFactory(DeadlineManagerSpanFactory)instead as it provides more configuration options.Kept for backwards compatibility, useJobRunrDeadlineManager.execute(String, String)instead.UseQuartzDeadlineManager.Builder.spanFactory(DeadlineManagerSpanFactory)which provides more configuration options.UseSimpleDeadlineManager.Builder.spanFactory(DeadlineManagerSpanFactory)instead as it provides more configuration options.Please useAbstractEventBus.Builder.spanFactory(EventBusSpanFactory)which is more configurablesince this method is not used for external use. This method is intended to deduce whether a givenEventMessageis aDomainEventMessageand 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 regularEventMessageaDomainEventMessageby any means. The only way to have a trueDomainEventMessageis by publishing events from within an Aggregate, by using theAggregateLifecycleoperations.in favor ofTokenSchema.Builder.setOwnerColumn(String)in favor ofTokenSchema.ownerColumnin favor ofMessageHandlingMember.attribute(String)in favor ofMessageHandlingMember.attribute(String)UseReflectionUtils.unwrapIfType(Type, Class[])insteadin favour of using {QueryBus.subscriptionQuery(SubscriptionQueryMessage, int)}in favour of using {QueryGateway.subscriptionQuery(String, Object, ResponseType, ResponseType)}. To set a backpressure strategy, use one of theonBackpressure..operators on the updates flux directly. Example:result.updates().onBackpressureBuffer(100)in favour of using {QueryGateway.subscriptionQuery(String, Object, ResponseType, ResponseType, int)}. To set a backpressure strategy, use one of theonBackpressure..operators on the updates flux directly. Example:result.updates().onBackpressureBuffer(100)in favour of using {QueryUpdateEmitter.registerUpdateHandler(SubscriptionQueryMessage, int)}UseSimpleQueryBus.Builder.spanFactory(QueryBusSpanFactory)instead as it provides more configurability.in favor use of {SimpleQueryBus.subscriptionQuery(SubscriptionQueryMessage, int)UseSimpleQueryUpdateEmitter.Builder.spanFactory(QueryUpdateEmitterSpanFactory)instead as it provides more configurability.in favour of using {SimpleQueryUpdateEmitter.registerUpdateHandler(SubscriptionQueryMessage, int)}Please useSubscriptionQueryResult.handle(Consumer, Consumer, Consumer)instead, to consciously deal with any exceptions with theerrorConsumer.in favor of using theXStreamSerializer.builder()to construct an instance using a configuredXStreaminstance. Using this shorthand still works, but will use anXStreaminstance 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.
-
Deprecated ConstructorsConstructorDescriptionPlease use
CommandCallback.wrap(CommandCallback)to wrap a command with a delegate and use theFailureLoggingCallback(org.slf4j.Logger, org.axonframework.commandhandling.CommandCallback<C, R>)to create this callbackPlease useCommandCallback.wrap(CommandCallback)to wrap a command with a delegate and use theFailureLoggingCallback(Logger)to specify you custom logger.in favor ofAbstractRoutingStrategy(RoutingStrategy)in favor of theAnnotationRoutingStrategy.builder()org.axonframework.commandhandling.distributed.AnnotationRoutingStrategy(Class<? extends Annotation>) in favor of theAnnotationRoutingStrategy.builder()in favor of theAnnotationRoutingStrategy.builder()in favor of theAnnotationRoutingStrategy.builder()in favor of theMetaDataRoutingStrategy.builder()in favor of theMetaDataRoutingStrategy.builder()Use theReplayToken.createReplayToken(TrackingToken)method instead.Use theReplayToken.createReplayToken(TrackingToken, TrackingToken)method instead.in favor ofDirectEventJobDataBinder(Serializer), as theSerializeris a hard requirement.
EntityManagerProviderwhich moved to jakarta.