Create a bidi-flow that is linked up to an ActiveMqSource and ActiveMqSink by their configuration name
Create an acknowledging bi-directional flow, with its FRONT-END-in hooked up to source
and its FRONT-END-out
hooked up to sink
.
Create an acknowledging bi-directional flow, with its FRONT-END-in hooked up to source
and its FRONT-END-out
hooked up to sink
. This constructor is intended for cases where responses are sent to a fixed ActiveMq
destination (i.e. the Sink)
This is a naive implementation of a bidirectional flow from/to ActiveMq; it assumes: - that a 1 on 1 correspondence (bijection) exists between elements sent to - and received from the BACK-END - that ordering is preserved between Out and In (see diagram); i.e. no mapAsyncUnordered, no foreachParallel, ideally no network-traversals; careful with dispatching to actors, etc. If this property cannot be upheld due to some stream-element's processing failing in an unexpected way, one will have to fail the graph - that at-least-once-delivery is acceptable on ActiveMqSink
This flow is practical for the typical use case of handling a request received from activemq, processing it with some bidi-flow, and dispatching a response to ActiveMq. The original requests gets acked once the response is sent.