Bindings allow us to control the way in which SOA Suite components interact with services. Different bindings provide different benefits, such as transactionality or better performance.
Generally when considering bindings, we do not have to worry too much about the low level details. The key questions we need to ask are:
Does this service already exist? In this case, we use the existing service without concerning ourselves about the bindings it uses.
Can this service be created by use of an adapter wizard? In this case, we use the appropriate adapter wizard to generate the required service without concerning ourselves about the bindings other than to make a note to create the appropriate JCA resource at the correct JNDI location.
Does this service require very high throughput? In this case, we may want to consider using an adapter or Java binding to improve performance, even if a SOAP binding already exists.
Does this service require true transactionality? In this case, we want to use...