Overview of JBossESB

Enterprises will always be heterogeneous; legacy systems are here to stay and will continue to grow. The ESB is the best solution to bridge these technologies by leveraging SOA. The best way in which is can accomplish this is to abstract all of the components - JBossESB does not mandate any implementations because it then becomes part of the legacy problem. SOA principles are used internally to JBossESB as well as externally: everything is a logical service and at the architectural level interacted with via messages.

For example, the diagram below shows the important aspect of the JBossESB architecture: everything is a service, including the bus, and all services are interacted with via messages. As such, even though at an implementation level services may reside within containers responsible for lifecycle management (e.g., init/destroy, start/stop, suspend/resume), it will be considered architecturally as though those services were plugged directly into a lifecycle bus and receiving appropriate messages. This figure also illustrates how services can be plugged into multiple buses concurrently.

The diagram below illustrates what is possible with JBossESB in the current 4.0Beta1 release. You should look at the various documents for further details.