JBI vs. SCA

, Jun 29, 2006

While I’ve put up a longer write-up at InfoQ regarding Ron Ten-Hove’s SCA critique, I try to keep expressions of my personal opinion to a minimum there. But here I can honestly say that I consider both SCA and JBI to be a waste of time.

IBM’s and BEA’s comments from the Approval Ballot are well worth repeating in full:

On 2005-06-20 IBM voted Abstain with the following comment:

IBM abstains because the JBI specification doesn’t represent a sufficient step forward in terms of what we believe our customers need, and above what they can already do. Many technologies and open specifications are available to the Java programmer today with more compelling interoperability and better mechanisms for component composition. IBM’s priority is to enable integration with the broadest range of platforms, applications, and existing business assets. This demands a language-neutral approach using today’s Web Services standards, and simpler programming and application models.

On 2005-06-20 BEA Systems voted Abstain with the following comment:

BEA believes that the JBI specification is an incomplete attempt to standardize the interfaces between multi-vendor infrastructure and contributes little to the usefulness of the Java platform for business application integration, one of the real pain point for our customers. It’s unfortunate that it’s name alone will result in significant confusion in the marketplace.

Regarding SCA, I admittedly haven’t yet had the time to really dig deep into it, so in that case, my dislike is purely a gut feeling.

On June 29, 2006 11:06 PM, Ron Ten-Hove said:

Interesting that you comment on my piece on SCA with some comments about JBI. That seems quite a non sequitur; JBI & SCA deal with very different areas of SOA.

As for the quotes from IBM & BEA, I think we can all read inbetween the lines well enough. Or at least those of use familiar with the integration software industry.

On June 29, 2006 11:24 PM, Stefan Tilkov said:

Ah well, Ron, that’s because it’s your piece on SCA. Had it been someone else, I probably would not have made the link to JBI … I guess this just goes with being a spec lead ;-)

On June 30, 2006 4:10 AM, Mike Herrick said:

I tend to agree. They are both seem fine if you are into clicky tools and like to be tortured.

I wish that all the vendor-pires would just implement AMQ and we could all just shut up and integrate the world.

http://fuzzypanic.blogspot.com/2006/06/advanced-message-queue-protocol.html

We either need AMQ or need to beef up HTTP.

On June 26, 2007 8:04 PM, Brian O'Neill said:

I originally shared the same opinion, but I honestly believe that JBI fills a tremendous gap. I tried to capture our experience with it on my blog.

On June 26, 2007 8:09 PM, Brian O'Neill said:

I guess anchor tags don’t work. Here is the link: http://weblogs.java.net/blog/boneill42/archive/2007/06/soaesbjbisca1.html