Posted by: Heather Clancy
Composite applications, Eclipse, Java, OSGi, SOA, SOA development
At EclipseCon this week, the Eclipse Foundation announced that it is forming a new open source community project “to develop and promote open source runtime technology based on Equinox, a lightweight OSGi-based runtime.”
Mike Milinkovich, executive director of the Eclipse Foundation, told SearchSOA that this is important news for architects and developers working on service-oriented architecture (SOA) projects for three reasons:
- “OSGi itself and Equinox as its implementation has a service-oriented component to it. It is a technology that you use to pull together services in a runtime.
- “EclipseLink, which provides persistence to enterprise applications for storing either relational data or XML Schema supports the acronyms enterprise architects love like FDO [Feature Data Objects]. You can get implementations of that specification through EclipseLink.
- “It is part of the Eclipse Swordfish project, which is a full SOA runtime.”
When Swordfish was announced earlier this year, Anne Thomas Manes, research director for Burton Group Inc., said OSGi added “real value” and is a good fit for the Eclipse plug-in philosophy.
“There’s a lot of nice features to OSGi,” Manes told SearchSOA. “You deliver software in something called a bundle. As part of the bundle it identifies the manifest of all the things that are in there and also identifies the dependencies that this code has. Then the OSGi runtime can look at it and say in order to deploy this I have to get these things that are listed in the dependencies, and get those installed first. It’s a very clean and elegant way to package stuff up. The idea here is that you are going to package up services using OSGi.”
There is currently a discussion thread on TheServerSide.com regarding Equinox, EclipseLink, OSGi and its relation to the Java Community Process work on the Java Persistence API (JPA 2.0).