P J, you seem to be engaged in an odd kind of FUD here.
Well, I find your interpretation of posting odd. So we're even, I guess.
First off you say:
ServiceMix has almost no relationship with SCA/SDO except in the most general sense.Which isn't entirely true because ServiceMix 3.0 does support SCA but I'll assume you didn't know that.
I got my information from the ServiceMix Web site:
In short, SCA and Tuscany address an important, but different problem from JBI and ServiceMix. The two models not only serve different purposes, but we believe that they are actually compatible, and that an SOA may require both in the near future.
It's true that I didn't have up-to-date information about them adding SCA support.
That's great news. It makes it more likely that others will follow.
You then go on to say:
But JBI is really a subset of SCA/SDO, which is much more like a reference architecture for SOA.
Which is also not true.
Why do you think this is not true?
I'm hardly the first person to say this. Check this out:
This article suggests that one possible future for JBI is to be a Java-only subset of SCA.
If JBI is a subset of SCA, it will be a VERY good one. And it will position Java very nicely as the leading (preferred) language in a multi-language environment.
In fact, of the two untrue statements, the first is probably more accurate since even your referenced articles and blog entries go on to say that JBI and SCA are complementary technologies.
Well at least we agree that they are complementary technologies.
Clearly you have a vested interest in SDO's but why the JBI FUD?
I've no idea why you think I've any negative opinions about JBI.
* Why is a Code Futures guy so worried about JBI?
Where have you seen a negative comment by me about even a single aspect of the JBI specification or any product that implements JBI?
My comments about BEA and IBM not supporting JBI were only in the context of a comparison of JBI and SCA.
Apart from the personal attacks, that's an excellent list of questions, by the way. It raises several key issues. I'll leave it up to someone else to respond since I don't want to run the risk you reading more into my comments than I intended!