Page History

...

JBI supports a standard deployment unit format; so you can hot deploy any JBI-compliant BPEL engine (or set of BPEL files into a BPEL engine), rule engine, transformation engine, scripting engine or other integration component (such as specific JBI binding components) directly into ServiceMix.

e.g. any JBI component developed in the Celtix project will automatically deploy and integrate seamlessly into ServiceMix. Similary you can just drop PXE the open source BPEL engine right in.

At the API level JBI and Mule differ quite a bit; though conceptually they are trying to do similar things. JBI is based on the idea of both component and container based routing - a JBI component can perform smart routing to endpoints. A JBI component can just communicate with its default service, letting the container do the routing for it. Or a JBI component can give the JBI container a hint of which endpoint to use (such as providing a service QName to use or specifying an operation QName) and then the JBI container can, if there are many available services to choose from, use some kind of policy negotiation or load balancing algorithm to choose which physical endpoint to choose. i.e. JBI is a cleaner abstraction for working with both logical and physical web service endpoints, WSDL and the standard WSDL defined message exchange patterns (MEPs).

...