Project: springxd
Issue XD-707: Support use of separate control and message transports
Control transport - Deploy/Undeploy requests Message transport - Inter module communication Currently complicated because starting a Job for example currently uses message transport vs control transport. Testing scenarios require local control and ability to switch to various message transports. One option is to change the interpretation of transport command line arg depending on SingleNode, Admin, or Container. e.g. SingleNode --transport rabbit (always use local for control messages) Admin (requires --transport, message transport does not apply) Container (enforces the same transport for message and control. Local optimization done via composite module) The other option is use a separate transport for control vs messages. Either way need to rationalize the design with respect to control and module messages
Story points: 2