Message bridge
A Message bridge is a relatively trivial endpoint that simply connects two channels or channel adapters. For example, you may want to connect a channel of type queue to a reqular channel so that the endpoint does not have to worry about any polling configuration. Instead, the messaging bridge provides the polling configuration.
By providing an intermediary poller between two channels, a Message bridge can be used to throttle inbound Messages. The poller’s trigger will determine the rate at which messages arrive on the second channel, and the poller’s "maxMessagesPerPoll" property will enforce a limit on the throughput.
Another valid use for a Message bridge is to connect two different systems. In such a scenario, Spring Integration’s role would be limited to making the connection between these systems and managing a poller if necessary. It is probably more common to have at least a Transformer between the two systems to translate between their formats, and in that case, the channels would be provided as the input channel and output channel of a Transformer endpoint. If data format translation is not required, the Messaging Bridge may indeed be sufficient.
Specifies when and how the reading task is executed.
Default global poller is used when empty
_id
Channel where output messages should be sent after (successfully) processing the input message.
You can select the nullChannel
here to silently drop the output messages.
Required
_id
Channel where output messages should be sent after (successfully) processing the input message.
You can select the nullChannel
here to silently drop the output messages.
Required
_id
Channel to consume the input messages from.
Required
_id
Channel to consume the input messages from.
Required
_id
Task executor to execute the scheduled tasks.
Default when empty: TaskScheduler with name 'taskScheduler', created if not exists.
_id
The channel that error messages will be sent to if a failure occurs in this poller's invocation. To completely suppress exceptions, provide a reference to the nullChannel here.
_id
Task executor to execute the scheduled tasks.
Default when empty: TaskScheduler with name 'taskScheduler', created if not exists.
_id
The channel that error messages will be sent to if a failure occurs in this poller's invocation. To completely suppress exceptions, provide a reference to the nullChannel here.
_id
The transaction manager responsible for handling the transactions.
Since this transaction manager should handle all transactions on the actual resource that this poller is polling, you cannot just use any transaction manager here. For example: if this poller is polling a database using JDBC, you should probably use a data source transaction manager on the same SQL data source that is used to perform the polling.
Required
_id
The transaction manager responsible for handling the transactions.
Since this transaction manager should handle all transactions on the actual resource that this poller is polling, you cannot just use any transaction manager here. For example: if this poller is polling a database using JDBC, you should probably use a data source transaction manager on the same SQL data source that is used to perform the polling.
Required