[ https://issues.jboss.org/browse/RTGOV-566?page=com.atlassian.jira.plugin.... ] Keith Babo commented on RTGOV-566: ---------------------------------- Support for SCA bindings was introduced to allow a "native" communication path into a SwitchYard application in support of the following use cases: 1) Inter-application communication between SwitchYard services. 2) Remote client access to a SwitchYard service. These cases are different from a traditional binding in that clients are dealing directly with the SY content and context. For other bindings (e.g. JMS, SOAP), the protocol-specific message needs to be mapped to the SY content and context, which is where a message composer and context mapper come in. If it is not possible to pass something via RemoteInvoker/RemoteMessage today, then we should definitely address that in the remote API and/or the SCA binding itself. My preference would be to avoid adding message composer support since clients should already be dealing with a native interface to SwitchYard. -- This message was sent by Atlassian JIRA (v6.3.1#6329)