Let's revisit the first solution, but this time with a file-based adapter. The configuration looks
conceptually the same as before, except the configuration for the adapter has changed, and with that has
gone a lot of the configuration for the JMS adapter, like the connection factory. Instead, you tell Spring
Integration about a different source from whence messages will come: the file system.
<?xml version="1.0" encoding="UTF-8"?>
<beans:beans xmlns:beans=" http://www.springframework.org/schema/beans"
<poller id="poller" default="true">
<interval-trigger time-unit="SECONDS" interval="10"/>
Nothing you haven't already seen, really. The code for file:inbound-channel-adapter is the only
new element, and it comes with its own schema, which is in the prologue for the XML itself.
The code for the service-activator has changed to reflect the fact that you're expecting a message
containing a message of type Message<java.io.File> .