OSGi

OSGi in the context of Java

IBM engineer Ian Robinson has a noteworthy blog post concerning OSGi. He points out areas of interest, questions to be answered.

On the other hand is the question of just how OSGi features in the programming model for enterprise applications. What is the web component model? The persistence model? How does the vast landscape of existing Java EE components begin to take some advantage from OSGi?

Robinson goes on to say the OSGi Alliance Enterprise Expert Group (EEG) is looking at these questions, and just how common Java EE technologies are addressed in an OSGi environment.

[On this one, a nod to old SearchSOA friend Daniel Rubio.]

Gartner cautions on Oracle middleware status

Oracle Fusion middleware is currently based on a group of product suites for SOA and BPM that are “assemblies of convenience,” argue Gartner analysts.

The suites are made up of Oracle’s existing product line and the technologies from its acquisition of BEA earlier this year, according to a brief report on the state of the current Oracle middleware offering, Oracle OpenWorld’s Middleware Message Is ‘Watch This Space,’ published earlier this month.

The Gartner analysts note that little was said about middleware in the announcements at Oracle Open World last month other than the announced plan to put Fusion in the Amazon cloud. The roadmap announced this past July for the full integration of the BEA products into Oracle’s middleware will not come until sometime in 2009, Gartner predicts.

Rather than judging the future of Oracle middleware by this interim marketing strategy, Gartner analysts recommend waiting for Oracle Fusion Middleware (OFM) 11g, due in the next six to 12 months.

That release ”will begin to implement the announced road map, and platform modernizations, such as support of OSGi Alliance technology and Service Component Architecture, expanded hot-pluggability, and the extensive use of Oracle Coherence XTP-distributed cache,” the report states.

What’s next for Java? Take a look at GlassFish.

I’m heading out to the JavaOne conference this week and it struck me that Java has had a very quiet year. Two years ago Sun launched Java EE 5 and almost immediately analysts began to call it a heavyweight dinosaur not likely to survive in an SOA world. Sun and others insisted Java would become more modular in the future, but last year Sun concentrated mostly on client development during JavaOne and it’s most momentous move during that past 12 months was to acquire MySQL, which doesn’t exactly point to any new directions for Java.

So what tea leaves can we read? I asked Brad Shimmin over at Current Analysis his thoughts and he said:

My impression with Java’s momentum is that it has reached a point where the platform needs to remain “consistent” top to bottom while affording specialization — much as Spring specialized as an alternative to EJB. I think Java EE 6 heads in this direction greatly with a highly modular approach that lets ISVs certify against particular aspects of the standard. That’s a good thing. Look at GlassFish for a vision of where this whole modularity thing is heading with its use of OSGi.

Well, sure enough, GlassFish v3 has OSGi support and a bunch of cool little subprojects like RESTful Web services, XML pipeline processing and an Ajax UI. Might we see the relationship between OSGi (and probably the Eclipse Foundation) and Java deepen? Now that would be revolutionary. The JCP page on Java EE 6 also mentions that Service Component Architecture could be part of the Java enterprise platform in the future.

Yet it makes you wonder if Java EE 6 has as much to offer the world as GlassFish v4 … or v5 even. Back in 2005, Sun had two hot new kids on the technology block - GlassFish and JBI. While JBI hasn’t gone much of anywhere, Sun continues to push and innovate with GlassFish. Why break a winning streak? What more can be done with the open source application server? Perhaps the biggest news this week won’t be what’s new for Java, but what’s coming up in GlassFish.

Eclipse forms OSGi community

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:

1. “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.
2. “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.
3. “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).