Binding services locally or remotely is not an innovation brought by ESB or JBI, but we have been doing it in multiple ways all through the years. In this chapter, we will explore the meaning of "Binding" and then look at how we can bind a remotely available service (in the form of an EJB component) to a middle-tier and expose it through a firewall friendly channel like HTTP. By the end of the chapter, you will appreciate how an extra indirection with a suitable tunneling will help to expose even technology specific API services, so that the service becomes technology agonistic.
We will cover the following in this chapter:
Meaning of binding
Apache SOAP binding
Binding a stateless EJB service to Apache SOAP
Running the sample