nl.nn.adapterframework.core

Interface ISender

All Superinterfaces:

org.springframework.context.ApplicationContextAware, org.springframework.beans.factory.Aware, IConfigurable, IConfigurationAware, INamedObject, IScopeProvider

All Known Subinterfaces:

IBlockEnabledSender<H>, ISapSender, ISenderWithParameters, IStreamingSender

All Known Implementing Classes:

Afm2EdiFactSender, AmazonS3Sender, BisJmsSender, BlockEnabledSenderBase, CmisHttpSender, CmisSender, CollectorSender, CommandSender, DelaySender, DirectQuerySender, EchoSender, EsbJmsSender, ExchangeFolderSender, FileSender, FileSystemSender, FileSystemSenderWithAttachments, FixedQuerySender, FixedResultSender, FtpFileSystemSender, FtpSender, HttpSender, HttpSenderBase, IbisJavaSender, IbisLocalSender, IdinSender, IdocSender, IdocSender, IdocSenderImpl, IfsaRequesterSender, IfsaRequesterSender, IfsaSimulatorJmsSender, ImapSender, IMSSender, JavascriptSender, JdbcIteratingPipeBase.MixedQuerySender, JdbcQuerySenderBase, JdbcSenderBase, JmsSender, JsonXsltSender, LdapSender, LocalFileSystemSender, LogSender, MailSender, MailSenderBase, MessageStoreSender, MongoDbSender, MQSender, MqttSender, MsalClientAdapter, MultipartHttpSender, NetStorageSender, ParallelSenders, ReloadSender, RestSender, ResultSet2FileSender, Samba1Sender, Samba2Sender, SambaSender, SambaSenderOld, SapSender, SapSender, SapSenderBase, SapSenderImpl, SchedulerSender, SenderBase, SenderSeries, SenderWithParametersBase, SenderWrapper, SenderWrapperBase, SendGridSender, ShadowSender, StreamingSenderBase, TibcoSender, WebServiceNtlmSender, WebServiceSender, XComSender, XfbSender, XmlJmsBrowserSender, XmlQuerySender, XmlValidatorSender, XsltSender, ZipWriterSender

@FrankDocGroup(order=20,
               name="Senders")
public interface ISender
extends IConfigurable

The ISender is responsible for sending a message to some destination.

Author:

Gerrit van Brakel

Method Summary

Modifier and Type	Method and Description
void	close() Stop/close the sender and deallocate resources.
void	configure() configure() is called once at startup of the framework in the configure method of the owner of this sender.
default boolean	consumesSessionVariable(String sessionKey) returns true if the sender or one of its children use the named session variable.
boolean	isSynchronous() When true, the result of sendMessage is the reply of the request.
void	open() This method will be called to start the sender.
SenderResult	sendMessage(Message message, PipeLineSession session) Send a message to some destination (as configured in the Sender object).
default Message	sendMessageOrThrow(Message message, PipeLineSession session)

Methods inherited from interface nl.nn.adapterframework.core.INamedObject

getName, setName

Methods inherited from interface nl.nn.adapterframework.core.IConfigurationAware

getApplicationContext, getName

Methods inherited from interface nl.nn.adapterframework.core.IScopeProvider

getConfigurationClassLoader

Methods inherited from interface org.springframework.context.ApplicationContextAware

setApplicationContext

Method Detail

configure

void configure()
        throws ConfigurationException

configure() is called once at startup of the framework in the configure method of the owner of this sender. Purpose of this method is to check whether the static configuration of the sender is correct. As much as possible class-instantiating should take place in the configure() or open() method, to improve performance.

Specified by:

configure in interface IConfigurable

Throws:

ConfigurationException

open

void open()
   throws SenderException

This method will be called to start the sender. After this method is called the sendMessage method may be called. Purpose of this method is to reduce creating connections to databases etc. in the sendMessage() method.

Throws:

SenderException

close

void close()
    throws SenderException

Stop/close the sender and deallocate resources.

Throws:

SenderException

isSynchronous

boolean isSynchronous()

When true, the result of sendMessage is the reply of the request.

sendMessage

SenderResult sendMessage(Message message,
                         PipeLineSession session)
                  throws SenderException,
                         TimeoutException

Send a message to some destination (as configured in the Sender object). This method may only be called after the configure() method is called.

The following table shows the difference between synchronous and a-synchronous senders:

	synchronous	a-synchronous
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.

Throws:

SenderException

TimeoutException

sendMessageOrThrow

default Message sendMessageOrThrow(Message message,
                                   PipeLineSession session)
                            throws SenderException,
                                   TimeoutException

Throws:

SenderException

TimeoutException

consumesSessionVariable

default boolean consumesSessionVariable(String sessionKey)

returns true if the sender or one of its children use the named session variable. Callers can use this to determine if a message needs to be preserved.