Composite Materials

JBI's new messaging model

The new public review draft of the JBI 1.0 specification is now available. This version introduces an important change to the JBI messaging model.

The previous Early Draft Review (EDR) version of the specification placed bindings (protocol handlers) and engines (internal service providers) into distinct roles. This has been significantly revised, to the better.

Rather than architecturally distinct bindings and engines, we now have JBI components, which serve as service providers, service consumers, or both. For example, an XSLT engine provides XML transformation services, while an inbound-only binding component serves as a (proxy) service consumer. A BPEL engine serves as a service provider (through its receive nodes), and consumer (invoke nodes).

These changes simplify the JBI APIs, eliminate the local binding component, and enable direct engine-to-engine and binding-to-binding service invocation.

I invite you to read the new draft of the Java(TM) Business Integration, available at the JCP. The major change I've outlined above, but there are numerous improvements, plus JavaDocs for all of the defined APIs. Please send your comments to jsr-208-comments@jcp.org.

Posted at 09:35PM Mar 08, 2005 by rtenhove in Java Business Integration  |  Comments[0]