Files
spring-integration-samples/advanced/dynamic-ftp
Gunnar Hillert 9effe2f9bc INTSAMPLES-33 Update to SI RC1 and Spring 3.1
1. Cleanup of pom.xml files
2. Standardizing version numbers
3. Updating dependency versions
4. Cleaning/Standardizing project names
5. Removing Schema versions in XML context files
2011-12-18 00:32:34 -05:00
..
2011-12-15 17:51:51 -05:00

This example demonstrates one technique for sending files to dynamic destinations.

See DynamicFtpChannelResolver. The resolve() method maps a customer to a channel, where the channel is defined in a separate application context for each customer. The application context property placeholders are configured using the Spring 3.1 Environment management by supplying a custom property source.

A real implementation would provide these properties based on the customer; this sample simply uses the customer as part of the host name.

The application context is loaded from the file in src/main/resources/...

DynamicFtpChannelResolverTests is a simple JUnit test case that verifies the same channel is used for the same customer each time, and that a different channel is used for a different customer.

FtpOutboundChannelAdapterSample shows how messages sent with a different customer header are routed to a different ftp adapter. It simply verifies that the correct UnknownHostException is returned.

Notice in the config file how an expression-based router is used to invoke the DynamicFtpChannelResolver to obtain a reference to the appropriate channel for the customer. Notice that the channel resolver is a simple POJO, invoked using SpEL...

<int:router input-channel="toDynRouter"
	expression="@channelResolver.resolve(headers['customer'])"/>