BEA to Join Eclipse Foundation - Page 2

By Darryl K. Taft  |  Posted 2005-02-21 Print this article Print

However, the Eclipse Web Tools Platform (WTP) Project is a top-level project for Eclipse, and sources said BEA is being considered as potential lead for that project. Right now, the WTP is co-lead by a representative from the Eclipse Foundations staff and a representative from the ObjectWeb Consortium, a European open-source software community. The Eclipse foundation has refreshed its platform for test and performance tools. Read more here.
Although BEA joining Eclipse and Borland enhancing its support is not news, the movement marks positive change, observers say.
"Borland is already a member [of Eclipse] and BEA is already funding a project through a third party called Instantiations [Inc.] to support the Beehive project (an open-source version of the BEA service-oriented architecture framework) in Eclipse," said Thomas Murphy, vice president of research services at Meta Group Inc. "BEA doesnt really want to be in the tools space. By going to Eclipse they have a platform that has broad support, [and] they dont have to continue to fill out their suite for lifecycle, etc., because it is already there from other vendors," Murphy said. BEA has shown its willingness to participate in open-source initiatives, first with its XMLBeans technology and then with the Beehive technology, which essentially is the open sourcing of the BEA WebLogic Workshop tool framework. BEA transferred an offshoot of that effort to the Eclipse Foundation as part of a project called Pollinate. Meanwhile, BEA donated both XMLBeans and Beehive to the Apache Software Foundation open-source community organization. Click here to read a review of BEAs XMLBeans. At last years TheServerSide Java Symposium, Benjamin Renaud, then deputy chief technology officer at BEA and current senior director of telecommunications products at the company, said BEA was open sourcing the WebLogic Workshop framework to spur tool innovation around it. Meanwhile, although Borland was a founding member of Eclipse, the company never based its core Java tools framework around the Eclipse platform. Yet, sources said Borland has now set its sights on the overall application lifecycle and may be willing to offer concessions on the IDE side of things. For instance, Eclipse could become Borlands core IDE, or the company could deliver an enhanced version of JBuilder or a JBuilder replacement based on Eclipse, sources said. Borland could be looking at Eclipse in the same way it views Microsoft Corp.s Visual Studio .Net. "In the same way, rather than trying to compete with Visual Studio, they are going to build around it," Murphy said. Next Page: Will Oracle be the only one left with its own toolkit?

Darryl K. Taft covers the development tools and developer-related issues beat from his office in Baltimore. He has more than 10 years of experience in the business and is always looking for the next scoop. Taft is a member of the Association for Computing Machinery (ACM) and was named 'one of the most active middleware reporters in the world' by The Middleware Co. He also has his own card in the 'Who's Who in Enterprise Java' deck.

Submit a Comment

Loading Comments...
Manage your Newsletters: Login   Register My Newsletters

Rocket Fuel