Project: springxd
Issue XD-1336: Allow easy integration with other types of message transports - remove enums for transport layers
If a third party messaging solution wants to be the transport layer in SpringXD they must currently fork the SpringXD code base and change the enums. Example: CommonDistributedOptions.ControlTransport currently limits to the following options (rabbit, redis). So if a third party like messaging system, like ZeroMQ, wanted to plug-in they would have to add to the enum. Here is another example where GemFire was used as the messaging system: https://github.com/charliemblack/spring-xd/blob/master/spring-xd-dirt/src/main/java/org/springframework/xd/dirt/server/options/CommonDistributedOptions.java#L38 All messaging enums should be removed for an extensible model.
Story points: 1