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:
Mark Fisher
2008-08-01 23:11:56 +00:00
parent 48826ec26e
commit 951226346a
41 changed files with 1193 additions and 351 deletions

View File

@@ -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"/>