Alan has over 25 years of professional experience in technology, including work as a software developer, architect, lead, and manager. This has included building complex systems fielded in some of the world’s most challenging environments. He’s an experienced Agile and DevSecOps coach and is currently the Director for External Outreach and Software Strategy for Lockheed Martin Corporate Engineering.

Alan has a degree in Computer Science from Embry-Riddle Aeronautical University, an MBA from the University of Minnesota, and a Master’s in Industrial Engineering from Georgia Tech. He lives in northern Virginia, halfway between Washington DC and Shenandoah National Park.

Recent Posts

image from OSGi Services: Automated Discovery and Service Lookup

OSGi Services: Automated Discovery and Service Lookup

This articles continues a series on declarative services in OSGi. We started with a basic OSGi bundle, then discussed architecting a multi-bundle application. Then we looked closer at declarative services and how to register them. All of this is fully demonstrated in an example application on GitHub. With the last article, we left off with a service interface, and implementation, and a few ways to tell the service registry about it.
read more
image from OSGi: Declarative Services and the Registry

OSGi: Declarative Services and the Registry

In two previous articles, I introduced building an OSGi bundle and the architecture of a multi-bundle OSGi solution. One of the key features of that multi-bundle solution in its associated GitHub repository is the use of OSGi declarative services. OSGi declarative services are the OSGi way to handle the instantiation problem: the fact that we want to code to interfaces, but we need some way to instantiate classes and some way to provide some concrete instance of an interface in order for the parts of our modular application to work together.
read more
image from Structure of OSGi Application with Declarative Services

Structure of OSGi Application with Declarative Services

So with our previous article and with a sample application, we made it all the way to an OSGi bundle that we can install in a Karaf container. However, so far we just build the bundle for our interfaces project, which just contains a single Java class. And that raises an important question: in a project with only five total Java classes, why did I go to the trouble to have four separate OSGi bundles, plus a separate Maven project for the Karaf feature repository XML file?
read more

More

Karaf Features and OSGi Services: A Bundle

Apache Karaf Features for OSGi Deployment

Karaf Features at Startup

TDD and CMM

All Posts