An early draft review of the JSR-208 a.k.a. JBI (Java Business Integration) is available for download. In a nutshell:
"JBI seeks to address this problem [vendor-specific integration soup] by creating a standards-based architecture for integration solutions, allowing third-party components to be assembled by the end user."
The key high-level constructs of JBI are:
- An environment is a container that provides a normalized WSDL-based messaging service ("NMS"), deployment, (re)configuration, deployment, and management.
- A service engine ("SE") is a "business logic driver". (This is where WS-BPEL fits into JBI.)
- A binding component ("BC") is a bridge between the internal normalized messaging service of the JBI environment and external protocols such as HTTP or JMS.
In terms of a WS-BPEL process living in a JBI environment, the process would be deployed in a SE that can execute WS-BPEL processes againt the NMS, and the concrete bindings for partnerLinks would be BC implementations.
One of the reasons that I'm excited about JBI is a little bit selfish: the portable runtime container that we built for PXE is similar to a JBI environment, so we've already been working in these terms for over a year... PXE will be available as a JBI component as soon as there are implementations that can host it.
Add a comment.
