StandardWorkflow
with a StandaloneProducer
with a
JmsReplyToDestination
.@Deprecated @ComponentProfile(summary="Deprecated: use StandardWorkflow+StandaloneProducer+JmsReplyToDestination instead", tag="workflow,jms") @ConfigDeprecated(removalVersion="4.0.0", groups=java.lang.Deprecated.class) public final class JmsReplyToWorkflow extends StandardWorkflow
StandardWorkflow
for use with JMS consumers and producers.
Generally it is preferred that you configure a StandardWorkflow
and make use the
appropriate JmsProducerImpl
implementation with a JmsReplyToDestination
instead.
Key differences to StandardWorkflow
are
ProduceDestination
is ignored; the appropriate
destination is derived from object metadataJmsProducerImpl
implementations must correspond to the associated
JmsConsumerImpl
implementation; i.e. PtpProducer
must be used with
PtpConsumer
.CoreConstants.KEY_WORKFLOW_SKIP_PRODUCER
, the producer is
always triggered.
In the adapter configuration file this class is aliased as jms-reply-to-workflow which is the preferred alternative to the fully qualified classname when building your configuration.
Modifier and Type | Class and Description |
---|---|
protected static class |
JmsReplyToWorkflow.ProducerType
Deprecated.
|
eventHandler, log, startTime, stopTime
PREVIOUS_GUID_KEY, WORKFLOW_ID_KEY
Constructor and Description |
---|
JmsReplyToWorkflow()
Deprecated.
|
Modifier and Type | Method and Description |
---|---|
void |
doProduce(AdaptrisMessage msg)
Deprecated.
This method contains the behaviour that varies between standard and request -reply workflows.
|
protected void |
prepareWorkflow()
Deprecated.
|
onAdaptrisMessage
closeWorkflow, handleMessage, initialiseWorkflow, resubmitMessage, startWorkflow, stopWorkflow
addConsumeLocation, addInterceptor, changeState, channelUnavailableWait, close, copyExceptionHeaders, disableMessageCount, friendlyName, getChannelUnavailableWaitInterval, getComments, getConsumer, getDisableDefaultMessageCount, getInterceptors, getMessageErrorHandler, getMessageLogger, getProduceExceptionHandler, getProducer, getSendEvents, getServiceCollection, getUniqueId, handleBadMessage, handleBadMessage, handleChannelUnavailable, handleProduceException, init, lastStartTime, lastStopTime, logSuccess, messageLogger, obtainChannel, obtainWorkflowId, prepare, processingStart, registerActiveMsgErrorHandler, registerChannel, registerEventHandler, requestClose, requestInit, requestStart, requestStop, retrieveActiveMsgErrorHandler, retrieveComponentState, sendEvents, sendMessageLifecycleEvent, setChannelUnavailableWaitInterval, setComments, setConsumer, setDisableDefaultMessageCount, setInterceptors, setMessageErrorHandler, setMessageLogger, setProduceExceptionHandler, setProducer, setSendEvents, setServiceCollection, setUniqueId, start, stop, workflowEnd, workflowStart
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
onAdaptrisMessage, onAdaptrisMessage
protected void prepareWorkflow() throws CoreException
prepareWorkflow
in class StandardWorkflowImpl
CoreException
public void doProduce(AdaptrisMessage msg) throws ServiceException, ProduceException
WorkflowImp
This method contains the behaviour that varies between standard and request -reply workflows. It is overridden in
RequestReplyWorkflow
.
doProduce
in interface Workflow
doProduce
in class WorkflowImp
msg
- the message to processServiceException
- not thrown by this implementationProduceException
- if any occur