WebLogic News Desk
BEA Systems Acquires SolarMetric in Aggressive Web Services Move
Claims Lead in Java EE 5 and Persistence Race
Nov. 3, 2005 05:30 AM
In a move almost certain to prompt a reaction from IBM and Microsoft and open-source web services competitor JBoss, BEA Systems has acquired the object persistence company, SolarMetric.
BEA management says the move gives it an early lead in the race towards Enterprise JavaBeans (EJB) 3.0 and Java EE 5 compatibility. SolarMetric, a privately-held company based in Austin, Texas, is known for its Kodo persistence engine, and supports both EJB 3.0 and Java Data Objects (JDO) programming models.
"The Kodo best-in-class persistence-engine firmly positions BEA as a market leader," said Wai Wong (pictured), executive vice president, products, BEA Systems, Inc. "Offering JDO within WebLogic via SolarMetric's Kodo will allow us to provide a richer experience and enhanced productivity to our extensive WebLogic customer user-base."
BEA's acquisition is based on the following insight: The draft EJB 3.0 standard focuses on persisting in-memory objects in relational databases. This means transient objects like shopping carts or ticket reservations can be stored over time. The JDO specification allows for persisting the objects in other ways as well -- the Kodo persistence engine has developer bindings for both EJB 3.0 and JDO, which allows developers to blend either standard in the same application. Customers have the choice to either use the JDO standard, get an early start on EJB 3.0 or add in EJB 3 .0 over time, as the specification is being finalized.
The acquisition also BEA's decade-long track record of successful technology acquisition, integration, enhancement and innovation, the company says. SolarMetric, widely respected for its persistence technology around JDO, will help BEA achieve faster time to market with its flagship WebLogic Server product.
BEA Vice President Bill Roth told WLDJ in an exclusive briefing, "Our overall acquisition strategy lately has been to do things that help us leapfrog the competition. By purchasing SolarMetric, we have the ability to deliver rock-solid persistence. This is something that makes developers lives easier when working with databases. It’s ultimately about productivity. This acquisition is a perfect follow-on to the M7 acquisition, which will allow us to take the lead in EJB3 developer as well as blended open source development as well."
About SOA News DeskSOA World Magazine News Desk trawls the world of distributed computing and SOA-related developments for the latest word on technologies, standards, products, and services and brings key information to you in a timely and convenient summary form.
#6 |
BleedBlue commented on 8 Nov 2005
Doesn't this just mean that IBM will push some CRAP to market early, and claim it is J5EE enabled? That means the loyalists will stick with second rate support for j5ee while their productivity wastes away.
|
#5 |
Infrastructuralist commented on 3 Nov 2005
]]BEA Vice President Bill Roth told WLDJ in an exclusive briefing, "Our overall acquisition strategy lately has been to do things that help us leapfrog the competition[[
But in leapfrogging IBM and Oracle, isn't the danger that those two companies combine somehow to *neutralize* this tactical coup by BEA?
|
#4 |
GamePlay commented on 3 Nov 2005
|||BEA Vice President Bill Roth told WLDJ in an exclusive briefing, "Our overall acquisition strategy lately has been to do things that help us leapfrog the competition."|||
And that's just what they've done. Leapfrogged IBM!
|
#3 |
BEA vs. IBM commented on 3 Nov 2005
This Web services space is hotting up.
|
#2 |
JDO rocks commented on 3 Nov 2005
JDO is more and more important it seems.
|
#1 |
WLDJ News Desk commented on 3 Nov 2005
BEA says today's move will give it an early lead in the race towards Enterprise JavaBeans (EJB) 3.0 and Java EE 5 compatibility, ahead of competitors like IBM. SolarMetric, a privately-held company based in Austin, Texas, is known for its Kodo persistence engine, and supports both EJB 3.0 and Java Data Objects (JDO) programming models.
|