The <channel-adapter/> now actually creates a channel instance rather than requiring another distinct channel object. Instead of configuring the poller on the channel-adapter, it is currently to be configured on the consuming endpoint just as if the <channel-adapter/> were any other pollable channel (e.g. <queue-channel/>).
This commit is contained in:
@@ -11,18 +11,15 @@
|
||||
|
||||
<message-bus/>
|
||||
|
||||
<channel id="channel1"/>
|
||||
<channel-adapter id="channel1" source="fileSource"/>
|
||||
|
||||
<channel id="channel2"/>
|
||||
<service-activator input-channel="channel1"
|
||||
output-channel="channel2"
|
||||
ref="exclaimer" method="exclaim">
|
||||
<schedule period="5000"/>
|
||||
</service-activator>
|
||||
|
||||
<channel-adapter source="fileSource" channel="channel1">
|
||||
<schedule period="10000"/>
|
||||
</channel-adapter>
|
||||
|
||||
<service-activator input-channel="channel1" output-channel="channel2"
|
||||
ref="exclaimer" method="exclaim"/>
|
||||
|
||||
<channel-adapter channel="channel2" target="fileTarget"/>
|
||||
<channel-adapter id="channel2" target="fileTarget"/>
|
||||
|
||||
<file-target id="fileTarget" directory="${java.io.tmpdir}/spring-integration-samples/output"/>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user