Chapter 7. Connecting components using bindings
This chapter covers
- Connecting services and references using SCA bindings
- Exposing SCA services using Web Services, CORBA, RMI, and JMS
- Integrating services exposed using Web Services, CORBA, RMI, JMS, or as EJBs from SCA
By this stage in the book you know how to implement SCA components and wire them together to create SCA applications. It’s now time for you to shift your focus and look outside the world of SCA and see how you can integrate your SCA applications with the rest of the world.
Often an SCA application will need to expose its services to existing business applications or make use of the services offered by them. This is done over a communications channel and protocol that’s understood by both parties. These existing business applications typically make use of a variety of communications protocols such as SOAP, CORBA, RMI, JMS, and so on.
This chapter is all about SCA bindings. You’ll see how SCA hides some of the complexities of handling communications protocols from the SCA application developer using SCA bindings. You’ll also see how SCA bindings allow the communications protocols to be changed with little effort.
This chapter uses components from the SCA Tours application to show how you can make services available to non-SCA applications using Tuscany SCA bindings. We’ll also demonstrate how other applications can expose their services to SCA components so their services can be invoked using Tuscany SCA bindings.