Neil Bartlett has released BndTools 1.0, an OSGi development environment for Eclipse. BndTools provides a way of developing OSGi bundles with Eclipse. Instead of defining dependencies by direct editing of the Manifest.MF, it uses Bnd files to drive a toolchain based on the Bnd tool.
WSO2 has added a new Ghost Deployer, a Cassandra-based Column Store Service, an Apache Subversion-based Deployment and an enhanced Load Balancer to both Carbon and Stratos. This functionality is also available on StratosLive.
The OSGi Alliance has made available the Early Draft specifications for the next release of the OSGi platform. As a draft specification, specific features may differ and some may be missing or replaced. Read on for what's new.
Mark Reinhold, Chief Architect for Java at Oracle, gave details of developments in Java 8 and beyond, and announced the GA release of JavaFX 2.0 during his keynote session at the JavaOne conference in San Francisco.
At the OSGi Community Event, Dr Graham Charters introduced the Modularity Maturity Model, a way of scoring where projects or organisations against how their modular developments score.
Eclipse Virgo, the evolution of the Spring DM OSGi server, has released version 3.0. The new release includes Gemini Web 2.0 and supports Tomcat 7 (with Servlet 3.0) as well as a new Jetty supported web container.
Apache Karaf has reached one year old today, as a top-level project at Apache. Karaf is a runtime package consisting of an OSGi framework (either Equinox or Felix), a command shell (Felix Gogo) and a number of useful utilities built in by default.
Oracle has today released Oracle JDeveloper 11g Release 2, along with an update to their meta MVC framework Oracle ADF (Application Development Framework). The release includes support for JSF 2.0 and Facelets, adds Hudson integration to Oracle TPC, and improves hot deployment for ADF. At the same time JDeveloper has been re-architected to sit on top of an OSGi backbone.
Yesterday, Mark Reinhold posted the first public draft of the future of modularity in Java. As it is a draft, there are a handful of issues that still need to be agreed on - but it represents the consensus of what modularity in Java should look like. And with IBM being involved, there's more emphasis on interoperability with OSGi than there has been in the past.
Late last month Google released Guice 3.0, a Java framework that implements the dependency injection (DI) design pattern. The motivation behind Guice was to make it easier for programmers to write DI code by reducing the need to write boilerplate factories. This article examines the new 3.0 features, loks at how Guice 3.0 supports Spring DI, and introduces Guice 4.1 (a.k.a. MiniGuice).
A new project on Google Code, the Pojo Service Registry, aims to provide an OSGi-lite mechanism for Java applications, but outside of a OSGi runtime. Instead of requiring all JARs to be bundles, it scans the startup classpath and emulates a bundle layer, whilst providing the service hookups that would be wired together in a full OSGi container.
Last week's JAX London included an OSGi specific day as well as others on Agile, Spring, JavaEE and tools. As well as the JAX Awards, other products were introduced such as the free GlobalsDB, an overview of Cloud Foundry, and Adobe Flex 4.5 running on top of iOS and on a demonstration BlackBerry playbook. Read on to find out more.
Manning have today published OSGi in Action, by Richard S Hall, Karl Pauls, Stuart McCulloch and David Savage. Written by long-term OSGi users and committers on the Apache Felix runtime, the depth of knowledge in the book comes across with subtleties and specific gotchas documented.
At EclipseCon 2011, the OSGi 4.3 specifications were announced and are available as a public final draft, to be released in the near future. Changes include adding generics to the core API, as well as a general purpose capability model to declare non-coding requirements between bundles. Read on for more information about what to expect.
Many consider the cost of migration onto OSGi expensive, but frequently this is conflated with the cost of modularity itself. Modularising a large, complex and heavily intertwined library is an expense that has no immediate benefits to the maintainers. However, if left to rot, the system will become more complex, intertwined and larger over time and the maintenance cost will increase.