And while many would only talk off the record about their thoughts regarding IBMs and BEAs motives, the outspoken leader of JBoss Inc., Marc Fleury, did not hold his tongue. In his blog, Fleury called SCA "a new shot at a closed standard for SOA."Indeed, Fleury said he believes JBoss continues to worry its bigger competitors. "We commoditized EE [Java Enterprise Edition] fast, capturing volume leadership, and they REALLY dont want to see the same thing happening to SOA and integration where they make so much of their money," Fleury wrote in his blog. "To add insult to injury, IBM and BEA are trying to open source the Tuscany project at Apache," Fleury added. JBoss wants to make its JEMS the industrys interoperable, open-source platform for SOA. Click here to read more. "Theres a set of projects in Apache around service infrastructure: SCA, the Web service metadata stuff were working on as part of Beehive, and some of the controls infrastructure that weve got for projects that are starting to build this notion of a programming model around actually doing service enablement and tying together disparate services with various transports," ONeil said. Moreover, "I still believe development can be easier," he said. "If you look at some of the things like Ruby on Rails and some of the frameworks that are happening outside of the Java space, there are efforts going on to continue to make development simpler on all platforms. "And I think that thats a trend that will continue and accelerate as adoption of the Java 5 VM [Virtual Machine] and some of the annotation and metadata standards that are available in that new virtual machine start to be used and applied inside frameworks to make things more declarative and more dynamic," ONeil said. "So I think ease of use is a trend well see in a big way going forward." Check out eWEEK.coms for the latest news, reviews and analysis in Web services.
Added Fleury as part of a lengthy post on the subject: "I wonder if SCA isnt IBM and BEAs response to Sun open sourcing SeeBeyond, or vice versa. But I dont think this is the heart of the matter anyway. I do, however, really believe IBM and BEA want to bypass the JCP [Java Community Process]. See, what happened to Java EE [Enterprise Edition] when JBoss joined was a rapid commoditization of that stack. We rapidly became the number one vendor. After all, why compete on a standardized technology when it is implemented by a credible and independent open source entity? I knew that when we joined the JCP EC [JCP Executive Committee], achieved standardization and captured volume leadership IBM was going to react. They did so by acquiring Gluecode and are botching it."