Deprecated API
Contents
- Interfaces
- Classes
- Exception Classes
- Annotation Interfaces
- Fields
- Methods
- Constructors
- Annotation Interface Elements
-
Deprecated InterfacesInterfaceDescriptionin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin favor of using
EntityManagerProviderwhich moved to jakarta.in favor of usingDeadLetterJpaConverterwhich moved to jakarta.in favor of the more genericMessageInterceptingMember
-
Deprecated ClassesClassDescriptionin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin through use of the AxonServer java connectorin favor of the
AggregateScopeDescriptorsince ehcache 2 is nearing eol, we addedEhCache3Adapterinstead, which uses ehcache 3.in favor of usingPagingJpaQueryIterablewhich moved to jakarta.in favor of usingSimpleEntityManagerProviderwhich moved to jakarta.this class is available for backward compatibility with instances that were serialized with Axon 2. UseGenericEventMessageinstead.this class is available for backward compatibility with instances that were serialized with Axon 2. UseGenericMessageinstead.this class is available for backward compatibility with instances that were serialized with Axon 2. UseMetaDatainstead.in favor of usingEventMessageDeadLetterJpaConverterwhich moved to jakarta.in favor of usingJpaDeadLetterwhich moved to jakarta.in favor of usingJpaSequencedDeadLetterQueuewhich moved to jakarta.in favor of theSagaScopeDescriptorin favor of usingJpaTokenStorewhich moved to jakarta.in favor of theGapAwareTrackingTokenin favor of theGlobalSequenceTrackingTokenin favor of usingEmbeddedEventStorewhich moved to jakarta.in favor of usingJpaEventStorageEnginewhich moved to jakarta.in favor of usingSQLErrorCodesResolverwhich moved to jakarta.In favor ofMultiStreamableMessageSource. This class belongs in themessagingmodule instead of theeventsourcingmodule.In favor ofMultiStreamableMessageSource.Builder. This class belongs in themessagingmodule instead of theeventsourcingmodule.in favor of usingBeanValidationInterceptorwhich moved to jakarta.As of release 4.4, replaced by usings on the monitor implementations. Useinvalid reference
Taginvalid input: 'to achieve the same behavior as this implementation.'in favor of usingGenericJpaRepositorywhich moved to jakarta.since moving to jakarta, as the genericserializedSagawas not handled well. There is aSagaEntrynot extending from this abstract class anymore, you might be able to use instead.in favor of usingJpaSagaStorewhich moved to jakarta.this class is available for backward compatibility with instances that were serialized with Axon 3. UseMongoTrackingTokeninstead.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.Replaced by theMessageHandlerLookupandMessageHandlerConfigurer, eliminating the need of an abstract implementation used for command and query registration.Replaced by theMessageHandlerLookupandMessageHandlerConfigurer.Replaced by theMessageHandlerLookupandMessageHandlerConfigurer.Replaced by theHandlerDefinitionFactoryBean.Use Spring Boot autoconfiguration or register the individual beans explicitly.Replaced by theHandlerDefinitionFactoryBean.Replaced by theHandlerDefinitionFactoryBean.Use Spring Boot autoconfiguration or register the individual beans explicitly.AnnotationDrivencontains a list of look-up and registration components to replace this component with.Use Spring Boot autoconfiguration or register the individual beans explicitly.Replaced by theSpringConfigurerandSpringAxonConfiguration.Replaced by theMessageHandlerLookupandMessageHandlerConfigurer.Replaced by theSpringConfigurer, which itself is aConfigurerimplementation.Replaced by theMessageHandlerLookupandMessageHandlerConfigurer.Replaced by theMessageHandlerLookupandMessageHandlerConfigurer.Replaced by theSpringAggregateLookupandSpringAggregateConfigurer.Replaced by theSpringConfigurerandSpringAxonConfiguration.Use Spring Boot autoconfiguration or register the individual beans explicitly.Instead of using a factory bean, consider retrieving the Repository directly from the Axon Configuration. Alternatively, when building a BeanDefinition, use theBeanHelperfactory methods to retrieve it.in favor of usingJpaAutoConfigurationwhich moved to jakarta.in favor of usingJpaEventStoreAutoConfigurationwhich moved to jakarta.in favor of usingContainerManagedEntityManagerProviderwhich moved to jakarta.in favor ofStubAggregateLifecycleExtensionto be used in combination with Junit 5In favor ofAxonServerContainerfollowing the merger of Standard and Enterprise edition into a single version.In favor ofAxonServerContainerfollowing the merger of Standard and Enterprise edition into a single version.in favor of theSimpleResourceInjectorVarious components have dedicated tracing SpanFactory interfaces since 4.9.0. This includes theCommandBus,EventProcessorandQueryBus. Use thedistributedInSameTraceof these instead.
-
Deprecated Exception ClassesException ClassDescriptionin through use of the AxonServer java connectorin favor of using
JSR303ViolationExceptionwhich moved to jakarta.
-
Deprecated Annotation InterfacesAnnotation InterfaceDescriptionUse Spring Boot autoconfiguration or register the individual beans explicitly. Check the "See also" list for which individual beans to register.Use Spring Boot autoconfiguration or register the individual beans explicitly. Check the "See also" list for which individual beans to register.
-
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 MethodsMethodDescriptionThrough use of the Axon Server Java Connector project.Through use of the Axon Server Java Connector project.Through use of the Axon Server Java Connector project, which enables the download message in absence of configured servers.Through use of the Axon Server Java Connector project.In favor of
AxonServerConfiguration.getPermits()This property is no longer used through adjustments in the Axon Server Java Connector project.Through use of the Axon Server Java Connector project, which enables the download message in absence of configured servers.In favor of theAxonServerConnectionManageritself being in charge of parsing theAxonServerConfiguration.getServers()list into aNodeInfocollection.In favor ofAxonServerConfiguration.setPermits(Integer)This property is no longer used through adjustments in the Axon Server Java Connector project.Through use of the Axon Server Java Connector project, which enables the download message in absence of configured servers.Not ued anymoreorg.axonframework.axonserver.connector.command.AxonServerCommandBus.Builder.spanFactory(SpanFactory) UseAxonServerCommandBus.Builder.spanFactory(CommandBusSpanFactory)instead as it provides more configurability.in favor of using theAxonServerQueryBus.Builder.queryExecutorServiceBuilder(ExecutorServiceBuilder)methodin through use of the AxonServer java connectorin through use of the AxonServer java connectorUseAxonServerQueryBus.Builder.spanFactory(QueryBusSpanFactory)instead as it provides more configurability.in favor of using the {AxonServerQueryBus.subscriptionQuery(SubscriptionQueryMessage, int)}in through use of the AxonServer java connectororg.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.in favor ofConfigurer.registerCommandHandler(Function), since thephaseof an annotated handler should be defined through theStartHandler/ShutdownHandlerannotation.in favor ofConfigurer.registerQueryHandler(Function), since thephaseof an annotated handler should be defined through theStartHandler/ShutdownHandlerannotation.aModuleConfiguration's phase is no longer used, as distinct phases might be necessary for any of the start or shutdown processes added in theModuleConfiguration.initialize(Configuration)methodin favor of maintaining shutdown operations in theComponent. Any lifecycle operations not covered through the components created by thisModuleConfigurationshould be added to theConfigurationinModuleConfiguration.initialize(Configuration)throughLifecycleOperations.onShutdown(int, LifecycleHandler)in favor of maintaining start operations in theComponent. Any lifecycle operations not covered through the components created by thisModuleConfigurationshould be added to theConfigurationinModuleConfiguration.initialize(Configuration)throughLifecycleOperations.onStart(int, LifecycleHandler)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.ownerColumnUseAbstractSnapshotter.Builder.spanFactory(SnapshotterSpanFactory)instead as it provides more configurability.in favor ofEventSchema.domainEventFields()Use thegapCleaningThreshold(int)in theJdbcEventStorageEngine.builder()insteadUse thegapTimeout(int)in theJdbcEventStorageEngine.builder()insteadin favor ofEventSchema.trackedEventFields()In favor ofMultiStreamableMessageSource.builder(). This class belongs in themessagingmodule instead of theeventsourcingmodule.in favor ofMessageHandlingMember.attribute(String)in favor ofMessageHandlingMember.attribute(String)UseReflectionUtils.unwrapIfType(Type, Class[])insteadin favor of using theEventProcessorLatencyMonitor.builder()in favor of using theEventProcessorLatencyMonitor.builder()Please use theGlobalMetricRegistry.registerEventProcessor(String, Function, Function)instead, which has separate tags for the latency metric.in favor of using theMessageTimerMonitor.builder()in favor of using theMessageTimerMonitor.builder()in favor of using theMessageTimerMonitor.builder()in favor of using theMessageTimerMonitor.builder()UseAbstractRepository.Builder.spanFactory(RepositorySpanFactory)instead, as it provides more configuration optionsthis field is no longer used to route commands to an aggregate. The aggregate to route a command to will be resolved with theTargetAggregateIdentifierannotated field in theCommandMessage's payload itself.in 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.This method has been previously used to report non-matchingMatcherresults. Has been replaced byReporter.reportWrongEvent(Collection, Description, Description, Throwable). The method is kept for api backwards compatibility only and my be removed in a future release.in favor ofTestExecutor.whenTimeAdvancesTo(Instant). This function incorrectly suggests you can proceed with other operations after calling it, which is made impossible due to theResultValidatorreturn typein favor ofTestExecutor.whenTimeElapses(Duration). This function incorrectly suggests you can proceed with other operations after calling it, which is made impossible due to theResultValidatorreturn typesince 4.6. UseTestExecutor.whenTimeAdvancesTo(Instant)methodsince 4.6. UseTestExecutor.whenTimeAdvancesTo(Instant)methodin favor ofStubDeadlineManager.getTriggeredDeadlines()Please use theMatchers.deepEquals(Object)instead. Using this method will lead to unwanted exceptions when ran on JDK 17 and up, due to adjustments in reflective access.Please use theMatchers.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.
-
Deprecated ConstructorsConstructorDescriptionPlease use
EventProcessorControlService(AxonServerConnectionManager, EventProcessingConfiguration, String, Map)to ensure processor settings are provided.Deprecated in favor of constructor with aSpanFactory. This constructor defaults to aNoOpSpanFactory.Deprecated in favor of constructor with aQueryBusSpanFactory. This constructor defaults to aDefaultQueryBusSpanFactorywith the providedSpanFactory.Please useCommandCallback.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.In favor ofMultiStreamableMessageSource(org.axonframework.eventhandling.MultiStreamableMessageSource.Builder). This class belongs in themessagingmodule instead of theeventsourcingmodule.in favor of using theRevisionSnapshotFilter.Builderin favor of theMessageTimerMonitor.builder()in favor of theMessageTimerMonitor.builder()Please use theAnnotationCommandTargetResolver.builder().useSagaSchema.BuilderinsteadIn favor ofSpringPrototypeAggregateFactory(Class, String, Map)to ensure all required fields are present for both polymorphic and non-polymorphic aggregates.In favor ofSpringPrototypeAggregateFactory(Class, String, Map)to ensure all required fields are present for both polymorphic and non-polymorphic aggregates.
-
Deprecated Annotation Interface ElementsAnnotation Interface ElementDescriptionthis field is no longer used to route commands to an aggregate. The aggregate to route a command to will be resolved with the
TargetAggregateIdentifierannotated field in theCommandMessage's payload itself.