TransportClientFactoryBean does not parse clusterNodes correctly [DATAES-470]

[spring-projects-issues]

Andy Wilkinson opened DATAES-470 and commented

The referenced commit has introduced two regressions:

1. StringUtils.split returns null if the input does not contain a comma. This means that a transport client that tries to use one node uses zero nodes instead.
2. When the input does contain a comma, the parsing is incorrect as it checks for a : in the clusterName field rather than the clusterNode local variable. This leads to an assertion failure stating that the port is missing

---

Reference URL: d66b2a6#diff-5e09aa5ede62dc7823cb0cf515cd5eadR97

Backported to: 3.0.9 (Kay SR9)

[spring-projects-issues]

Oliver Drotbohm commented

That's in place. I took the chance to extract the parsing logic into a value object to finally properly unit test it