@Target(value=TYPE) @Retention(value=RUNTIME) @Component public @interface Archive
ArchivePollingContainer.
 Template can be provided using EventTemplate marked on a general
 method that returns the template.
TransactionalEvent| Modifier and Type | Optional Element and Description | 
|---|---|
| String | archiveHandlerThe name of the bean that is the  ArchiveOperationHandlerthis
 container will use. | 
| boolean | autoStartSet whether this container will start once instantiated. | 
| int | batchSize | 
| int | concurrentConsumersSpecify the number of concurrent consumers to create. | 
| String | gigaSpaceThe name of the bean that is the  GigaSpacethis container will
 use. | 
| int | maxConcurrentConsumersSpecify the maximum number of concurrent consumers to create. | 
| boolean | performSnapshotIf set to  truewill perform snapshot operation on the provided template before
 invoking registering as an event listener. | 
| long | receiveTimeoutSet the timeout to use for receive calls, in milliseconds. | 
| long | recoveryInterval | 
| boolean | useFifoGrouping | 
| String | valueThe value may indicate a suggestion for a logical component name, to be turned into a Spring
 bean in case of an autodetected component. | 
public abstract String value
public abstract int concurrentConsumers
Specifying a higher value for this setting will increase the standard level of scheduled concurrent consumers at runtime: This is effectively the minimum number of concurrent consumers which will be scheduled at any given time. This is a static setting; for dynamic scaling, consider specifying the "maxConcurrentConsumers" setting instead.
Raising the number of concurrent consumers is recommended in order to scale the consumption of events. However, note that any ordering guarantees are lost once multiple consumers are registered. In general, stick with 1 consumer for low-volume events.
public abstract int maxConcurrentConsumers
If this setting is higher than "concurrentConsumers", the listener container will dynamically schedule new consumers at runtime, provided that enough incoming messages are encountered. Once the load goes down again, the number of consumers will be reduced to the standard level ("concurrentConsumers") again.
Raising the number of concurrent consumers is recommended in order to scale the consumption of events. However, note that any ordering guarantees are lost once multiple consumers are registered. In general, stick with 1 consumer for low-volume events.
public abstract long receiveTimeout
NOTE: This value needs to be smaller than the transaction timeout used by the transaction manager (in the appropriate unit, of course).
public abstract boolean performSnapshot
true will perform snapshot operation on the provided template before
 invoking registering as an event listener.GigaSpace.prepareTemplate(Object), 
AbstractEventListenerContainer.setPerformSnapshot(boolean)public abstract boolean autoStart
Default is true. Set to false in order for this container to be
 started using AbstractEventListenerContainer.start().
public abstract String archiveHandler
ArchiveOperationHandler this
 container will use.
 Note, this is optional. If there is only one ArchiveOperationHandler
 defined in the application context, it will be used.
Copyright © GigaSpaces.