public class RequiresNewSagaProcessor extends SagaProcessor
camelContext, completionMode, sagaService, stepprocessorshutdown, shuttingdown, started, starting, stopped, stopping, suspended, suspending| Constructor and Description |
|---|
RequiresNewSagaProcessor(CamelContext camelContext,
Processor childProcessor,
CamelSagaService sagaService,
SagaCompletionMode completionMode,
CamelSagaStep step) |
| Modifier and Type | Method and Description |
|---|---|
boolean |
process(Exchange exchange,
AsyncCallback callback)
Processes the message exchange.
|
getCurrentSagaCoordinator, getSagaService, handleSagaCompletion, ifNotException, ifNotException, setCurrentSagaCoordinator, toStringdoShutdown, doStart, doStop, getProcessor, hasNext, next, process, processNext, setProcessor, setProcessordoResume, doSuspend, getStatus, getVersion, isRunAllowed, isStarted, isStarting, isStopped, isStopping, isStoppingOrStopped, isSuspended, isSuspending, isSuspendingOrSuspended, resume, shutdown, start, stop, suspendpublic RequiresNewSagaProcessor(CamelContext camelContext, Processor childProcessor, CamelSagaService sagaService, SagaCompletionMode completionMode, CamelSagaStep step)
public boolean process(Exchange exchange, AsyncCallback callback)
AsyncProcessorProcessor.process(org.apache.camel.Exchange), but the caller supports having the exchange asynchronously processed.
If there was a failure processing then the caused Exception would be set on the Exchange.process in interface AsyncProcessorprocess in class DelegateAsyncProcessorexchange - the message exchangecallback - the AsyncCallback will be invoked when the processing of the exchange is completed.
If the exchange is completed synchronously, then the callback is also invoked synchronously.
The callback should therefore be careful of starting recursive loop.Apache Camel