Michael Rowley wrote very detailed analysis comparing SCA and JAX-WS.
- “JAX-WS is very explicitly about supporting the use of web services that are advertised with WSDL and most likely use SOAP over HTTP as the transport mechanism. SCA assumes that clients and authors of services don’t care. They do care that it is remote, but they don’t necessarily care whether WSDL will be used, and they certainly don’t care what the transport mechanism is.”
- “In addition to being less tied to WSDL, SCA also has a few capabilities that aren’t present in JAX-WS. For example, the SCA programming model supports the concept of conversational services and bidirectional services.”