Not logged in | Login
Top N Myths About Open ESB
Here are some of the common misconceptions about Open ESB on external posts and articles. Where appropriate, evidence and examples are provided.
On the contrary. Open ESB is a community and is actually part of the wider GlassFish community. The community was started by Sun and thus includes a number of Sun employees and some of these are content developers and code commiters. However, since its inception the community has grown and diversified and there are many others contributing ideas, new code, bug fixes and feedback. Some of the code contributed is in the form of binding components from vendors who are listed on the partner page.
The community is becoming increasingly more active and a look at the mailing list posts is good evidence of that. In fact, a quick browse through this will prove without question that there are many evaluators and users of Open ESB outside of Sun. Coupled with the large, knowledgeable base of users within Sun, it makes for a vibrant community with quick and assertive responses and an ever-growing set of resources to support the community.
Open ESB includes a BPEL service engine with associated tooling in NetBeans which allows orchestration of services. Due to the inclusion of JBI in Open ESB, which promotes service-based integration, BPEL is frequently used in the many examples of Open ESB but it is in no way mandated. Alternative approaches for mediation and orchestration include using Java logic via the Java EE service engine, using the Apache Camel service engine with Open ESB and even using IEP for complex event processing. For instance, see Mark Foster's example of invoking reusable transformations from different bindings without BPEL.
It is also possible to mediate between JBI components without using any service engine if that is what is required. Michael Czapski has good coverage of this on this blog entry.
One of the goals of OpenESB v3 or Project Fuji is to simplify the means of routing and mediating messages between service interfaces without a full orchestration language like BPEL. The use of a Domain Specific Language (DSL) called Integration Flow Language (IFL) is of relevance here as is the use of OSGi interceptors to plug in logic to the runtime ESB.
Project Open ESB and its community addresses the concerns of integration using an ESB. Many of the components contributed are currently JBI components but this is not a requirement. Open ESB includes non-JBI components as well such as the sun-jms-adapter which is a JCA component.