Reputation: 113
I'm implementing the TCP client using the Spring Integration. The requirements are: 1. Through the UDP connection (from somewhere) receive the ip or host address of the TCP server. 2. Open TCP connection to the server, to the destination host from previous step and send some business data to this server.
I use the Spring Integration framework, version "2.2.0.RELEASE", and the problem is that in the default configuration of the tcp-connection-factory the host attribute should be "hardcoded" in xml. For example:
<ip:tcp-connection-factory id="client" type="client" host="localhost" port="1234" single-use="true"/>
The question is how to avoid the static definition of the destination host in application context, and be able to 'lazy' initialise the tcp-connection-factory when the destination host will be known.
I know that this flow could be easily implemented by the standard Network APIs of Java, and the question is specific about the Spring-Integration API
Upvotes: 1
Views: 1175
Reputation: 8842
It's not currently possible/easy - even if you customize or extend the class for tcp-connection-factory to be able to connect to changing hosts. There is an open new feature request in JIRA to provide this functionality.
Upvotes: 0
Reputation: 121272
As far as <int-ip:tcp-connection-factory>
provides some instance of AbstractConnectionFactory
. And from other side <int-ip:tcp-outbound-channel-adapter>
applies that instance via connection-factory
, so, there is no stops to implement your own RoutingConnectionFactory
.
The implementation may rely on some value from ThreadLocal
. The idea is here:
Upvotes: 1
Reputation: 174554
At this time, the configuration is static.
You could however use a similar technique to that used in the dynamic ftp sample which configures ftp outbound adapters at runtime.
Upvotes: 1