OSGi enables Java code to be divided cleanly into modules known as bundles with access to code and resources controlled by a class loader for each bundle. OSGi services provide an additional separation mechanism: the users of an interface need have no dependency on implementation classes, factories, and so forth. The following case study aims to make the above advantages ...
Read More »Home »
Java Modularity Approaches – Modules, modules, modules
I think everybody will agree that writing modular applications and modularity in general is a good thing. But how does support for modularity look like, both from the Java and Scala languages and various Java/Scala frameworks? There’s a lot of different approaches! Let’s look at some of them. Below “protection” means how well modules are separated either at compile-time or ...
Read More »JBoss Modules Example – Modular Web Application
Recently I read Why there is no standard for developing real modular web applications? by Patroklos Papapetrou (also featured in Java Code Geeks). Inspired by this article I decided to check JBoss Modules in action. This post describes my experiment step by step. I’ve started with the following goal in mind – to create a web application using some service ...
Read More »Real modular web applications: Why there is no standard for developing them?
OSGI, SpringSource, Jboss Modules, J2EE and the list never ends.All these technologies promise to their end users/developers the same thing which is more or less java modular web applications (?). How many of us out there, though, have actually tried to develop a REAL modular software system in Java? How many of us have managed to get it done? You ...
Read More »