Monday Jun 04, 2007
Wednesday Apr 11, 2007
By rtenhove on Apr 11, 2007
Some interesting bits:
"Both SCA and JBI are focused on helping developers construct and compose services so it is natural to assume that they are competitors; however, this is not the case. While both can be used separately, they are also effective to use together because they focus on different aspects of the larger service composition problem.
"The reason this is possible is that SCA and JBI target different audiences. The SCA specifications target end users. They describe how to implement, assemble and deploy applications composed from services. As such, the target audience for these specifications is people working in the roles of developer, assembler and deployer respectively."
That pretty well summarizes the situation, as it exists with JBI 1.0. One of the possible outcomes of JSR 312 (JBI 2.0) is an improvement in the alignment between the two technologies. Such an improvement would allow the technologies not only to co-exist (as is the case today), but also would eliminate what small "impedance mismatches" exist in the areas of deployment and metadata.
- Book review: Symmetry, A Journey into the Patterns of Nature
- OpenESB about to hit a major milestone
- Is JBI an ESB?
- JavaOne 2008
- BPEL4People and WS Human Task submitted to OASIS
- Security leads to insecurity?
- SOA lessons learned from business process automation
- SOA services != RPC
- ZapThink should rethink SCA and JBI
- ANTLR 3