public class ReloadSender extends SenderWithParametersBase
It is possible to set the name of the configuration with the parameter 'name'.
You can dynamically set 'forceReload' attribute with the parameter 'forceReload'.
parameterNamesMustBeUnique, paramList
log
Constructor and Description |
---|
ReloadSender() |
Modifier and Type | Method and Description |
---|---|
boolean |
getForceReload() |
SenderResult |
sendMessage(Message message,
PipeLineSession session)
Send a message to some destination (as configured in the Sender object).
|
void |
setForceReload(boolean forceReload)
reload the configuration regardless of the version
|
addParameter, checkStringAttributeOrParameter, configure, consumesSessionVariable, getParameterList, getParameterOverriddenAttributeValue, getParameterOverriddenAttributeValue, getParameterValueList
close, createBean, getLogPrefix, getName, open, setApplicationContext, setName
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
close, isSynchronous, open, sendMessageOrThrow
getName, setName
getApplicationContext, getName
getConfigurationClassLoader
public SenderResult sendMessage(Message message, PipeLineSession session) throws SenderException, TimeoutException
ISender
configure()
method is called.
The following table shows the difference between synchronous and a-synchronous senders:
synchronous | a-synchronous | |
---|---|---|
ISender.isSynchronous() returns | true | false |
return value of sendMessage() is | the reply-message | the messageId of the message sent |
the correlationID specified with sendMessage() | may be ignored | is sent with the message |
a {link TimeOutException} | may be thrown if a timeout occurs waiting for a reply | should not be expected |
Multiple objects may try to call this method at the same time, from different threads.
Implementations of this method should therefore be thread-safe, or synchronized
.
SenderException
TimeoutException
public void setForceReload(boolean forceReload)
public boolean getForceReload()
Copyright © 2023 Frank!Framework. All rights reserved.