Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

BEA Executive Defends Decision Not To Join Eclipse: Page 2 of 3

"What's the point of joining Eclipse if you're not going to actively use the Eclipse framework," Cotter told CRN Wednesday.

BEA is intent on maintaining control over the Workshop GUI and its specific features, which link to the WebLogic software stack to facilitate development on BEA's application server, portal and integration server, Cotter said. To rebuild Workshop on Eclipse would mean relinquishing control over that intellectual property, and is not in line with BEA's overall direction, he said.

"Sure, we could throw Workshop code away and join Eclipse, but we have a lot invested in Workshop and a lot we want to do to drive our platform forward using [the tool]," Cotter said. "Controlling the code base and how we craft the IDE and having the Workshop code base as an asset [is the] easiest way and most efficient way for us to deliver on value-added features for our customers. Owning that destiny and direction makes a ton of strategic sense."

It is possible for companies to join the Eclipse Foundation without actually building their tool on the IDE. However, Cotter said BEA is not interested in this kind of membership.

BEA and IBM are bitter rivals in the Java application server market, so it comes as little surprise that BEA has not joined the Eclipse Foundation or used the Eclipse IDE, software created by IBM in November 2001 as a common foundation for multiple developer tools. The foundation became an independent open-source organization in February.