Notes about JBI..

1、JBI is a pluggable architecture consisting container and plug-ins.The container hosts the plug-ins components that communicate via message routers. Architecturally, components interact via an abstract service model- a messaging model that resides at a level of abstration above any particular protocol or message-encoding format. JBI is an SOA: it treats components as service providers and consumers.(Is that what SOA like in nature ?)
2、Abstractions are quite useful, however, without concrete instances of them , it is impossible to get the real work done. JBI uses the Web Services Description Language (WSDL) for both abstract and concrete specification of its component messaging model. The abstract model defines message types that service providers and consumers can exchange, abstract operations comprising those messages, and service types or interfaces that group related operations together. The concrete model defines binding types to specify protocols, endpoints to specify  concrete communication details for reaching services, and services that group related endpoints to specify actual service instances.
3、The JBI environment is a collection of components reside within a single Java virtual machine(JVM).Services can reside outside the JBI environment and connect into it via binding components(BCs), or they can reside within subcontainers, called service engines(SEs),that live directly within the JBI environment. Services connected into to a JBI environment, whether through an SE or a BC, communicate with each other via the normalized message router,which is the JBI environment's primary service.
4、BCs and SEs communicate with the NRM via delivery channels, which are objects that provide methods for sending and accepting messages and for creating message-exchange factories. These factories allow service consumers to create specific message-exchange instances for use with target services.