Show Table of Contents
3.6. Service Binding
A service binding is used to define an access method for a composite service. Composite services can have multiple bindings, which allows a single service to be accessed in different ways. In most cases, a service binding represents a protocol or transport adapter (for example, SOAP, JMS, and REST). An important exception to this rule is the SCA binding, which allows services across applications in the same runtime to be wired together in memory. Regardless of the underlying binding details, a binding must always be used to facilitate inter-application communication in SwitchYard.
Figure 3.7. Service Binding
Example 3.6. Sample Corresponding XML
<sca:composite name="example" targetNamespace="urn:example:switchyard:1.0">
<sca:service name="ServiceA" promote="Routing/ServiceA">
<sca:interface.wsdl interface="ServiceA.wsdl#wsdl.porttype(ServiceAPortType)"/>
<soap:binding.soap>
<soap:wsdl>ServiceA.wsdl</soap:wsdl>
</soap:binding.soap>
</sca:service>
</sca:composite>
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.