Regular InfoQ Java contributor Dr. Alex Blewitt has recently published a follow-up to last year’s "Eclipse 4 Plug-in Development by Example”. Called “Mastering Eclipse Plug-in Development,” the book, like its predecessor, is essentially a tutorial, but it assumes that you are already familiar with the basics of building plug-ins for the Eclipse IDE, and rapidly dives into advanced topics.
Peter Kriens, one of the driving forces behind OSGi, announced his return to the OSGi Alliance, where he served as director for 11 years until early 2012. InfoQ caught up with Peter to discuss his return, OSGi, and his latest project jpm4j.
Java Application Architecture: Modularity Patterns with Examples using OSGi is Kirk Knoernschild's seminal book on a pattern catalogue for modular systems design. Starting with an overview of the arguments for modularity, the main section in the book introduces eighteen categorised patterns for module development, and concludes with an OSGi example. InfoQ spoke to Kirk to find out more about it.
Mulesoft recently released Mule 3, their next generation ESB platform. InfoQ caught up with Ross Mason to learn more about the product release and learn about the new features in the product offering.
The fourth of the Modular Java series covers declarative modularity. It describes how components can be declaratively defined and wired together, without having a code dependency on OSGi APIs. 11
Porting great infrastructure to OSGi often means solving complex classloading problems. This article is dedicated to one of the the hardest issues in this area: dynamic code generation. 3
This third part of the Modular Java series discusses dynamic modularity, how a bundle's classes are resolved, how they can come and go, and how they can communicate with each other. 2
This second part of the Modular Java series discusses static modularity, the creation of bundles, how to install them into an OSGi engine and how to set up (versioned) dependencies between bundles. 3
Over the last few years, modularity for Java has been an active discussion topic. Several JSRs show modularity is necessary for Java's evolution. What does modularity mean, and why should you care? 4
This article presents one developer's approach to dealing with the "fiendishly hard" OSGi issue of service dynamics. The basic problem is described and two different solutions are proposed. 2
In a new article, Eric Newcomer writes about the current status of distributed OSGi and explains the reasons for standardizing it in the first place. 3
Java module systems have received lots of attention. In this article Lukas Krecan gives a round-up of the current solutions & presents his concern on solutions like project Project Jigsaw & JSR-294. 9