With Envelope Wrapper we already dealt with the situation where an external message is incompatible with our local Actor System. We used to Envelope to both adapt the external message to one locally acceptable, and we also designed the Envelope to reply to the originating external system. This made dealing with the external messaging system, …
With the Envelope Wrapper an incompatible message from an external system is made compatible with our Actor System. Yet, the opposite situation may be true; a message that the local Actor System needs to send is not compatible with an external system because the external system needs more content than the local system stores. What …
We’ve discussed a few different ways to use Return Address with the Actor Model, which allows a message-receiving Actor to reply to an Actor other than the direct sender or forwarder of the message. Sometimes, however, it might work out for the best if your messages themselves support the means to dispatch to a reply-to …
Since you understand how to implement a Request-Reply using Actor Model, what if you want your Request receiver to Reply to an Actor at an Address other than the direct message sender? Well, that’s the idea behind the Return Address pattern, and one that we can implement in a few different ways.
This is the first in a series of simple posts about using Actor Model to implement the EAI Patterns. The patterns are from the book Enterprise Integration Patterns, by Gregor Hohpe and Bobby Woolf. Information about the book and the patterns are found at the previously referenced link.
