Prior to this release, an Eagle service client creates its own AEP engine instance. This release adds the ability for a user of the service client to supply an AEP engine for it to use rather than create a new one.

Note: Although this functionality can be used by an end user, this is primarily for use by a peerEagle service to perform asynchronous request-reply with the the service

Prior to this release, two peer Eagle services could not perform request-reply with each other. This release implements the ability to do so. When a service is declared as peer of another service, this release will perform the following:

• Automatically include the peer service's client in the service runtime
• Instruct the peer service client to use the service's engine
• Generate handlers for the peer service client's response messages
• Generate injectable MessageSender instances for the peer service event and request messages