@ComponentProfile(summary="The default NO-OP exception handler", tag="error-handling,base") public class NullProcessingExceptionHandler extends RootProcessingExceptionHandler
In the adapter configuration file this class is aliased as null-processing-exception-handler which is the preferred alternative to the fully qualified classname when building your configuration.
log
Constructor and Description |
---|
NullProcessingExceptionHandler() |
Modifier and Type | Method and Description |
---|---|
void |
close()
Closes the component.
|
void |
handleProcessingException(AdaptrisMessage msg)
Handles a message that has deemed to have failed.
|
boolean |
hasConfiguredBehaviour()
Simply report back to the owning component whether or not this ProcessingExceptionHandler is actually going to do anything.
|
void |
init()
Initialises the component.
|
void |
prepare()
Prepare for initialisation.
|
void |
registerWorkflow(Workflow w)
Register a workflow against this error handler.
|
void |
start()
Starts the component.
|
void |
stop()
Stop the component
|
changeState, getAlwaysHandleException, getParent, getUniqueId, notifyParent, onChildError, registerDigester, registerParent, requestClose, requestInit, requestStart, requestStop, retrieveComponentState, retrieveDigester, setAlwaysHandleException, setUniqueId
public void handleProcessingException(AdaptrisMessage msg)
ProcessingExceptionHandler
public void registerWorkflow(Workflow w)
ProcessingExceptionHandler
w
- the workflow to register.public void init() throws CoreException
ComponentLifecycle
Component initialisation includes config verification, creation of connections etc.
CoreException
- wrapping any underlying Exception
spublic void start() throws CoreException
ComponentLifecycle
Once a component is started it should be ready to process messages. In the case of
AdaptrisMessageConsumer
, calling start will begin message delivery.
CoreException
- wrapping any underlying Exception
spublic void stop()
ComponentLifecycle
A stopped component is not expected to be ready to process messages. In the case of
AdaptrisMessageConsumer
, calling stop will pause message delivery. Throwing a
RuntimeException
may cause unintended consequences
public void close()
ComponentLifecycle
A closed component should release any connections it uses, etc. and clean up completely.
Throwing a RuntimeException
may cause unintended consequences
public void prepare() throws CoreException
ComponentLifecycleExtension
CoreException
public boolean hasConfiguredBehaviour()
ProcessingExceptionHandler