Supporting Dual MEP:s reusing same service

The tenets of SOA...."loosely coupled" and "autonomous" services.
Here i'll show how you can reuse the same service, e.g the same service implementation, supporting different Message Exchange Patterns.
- synchronous two-way request-response pattern
- asynchronous one-way request pattern

* Reusing the same orchestration(service) for both synchronous and asynchronous interaction
* MsgBox direct-binding(e.g no logical/orchestration ports) -> more autonomous and self-contained
* To fulfil the above you have to copy all(*) BTS subscription-properties from inbound to outbound message. You also have to set the property (BTS.RouteDirectToTP = true).
* One way to determine if the request originates from a one-way or two-way conversation is to evaluate the property (BTS.EpmRRCorrelationToken exists "inboundmessage")