Holistic Enterprise-Ready Application Security Architecture Framework
We have already demonstrated in the tutorial "Automatic testing of OSGi Bundles" how the use of Spring and Spring Dynamic Modules vastly simplifies the implementation of OSGi Bundles. If we want to use the same concepts on the RCP layer, though, several additional challenges have to be mastered. This tutorial shows how a flexible solution can be built by using the appropriate technologies and thus keeping the advantages of both worlds.
Many developers working with Maven appreciate its flexibility and the simplicity of creating an automatic build environment. The central management and lookup of dependencies is only one of the advantages. Eclipse RCP, which is based on OSGi, offers with its modular structure and its included components a comfortable base for the development of Rich-Client applications. In practice, though, the interaction of these both "worlds" poses a challenge, which should not be underestimated. This tutorial application was developed within the scope of the and shows how we combined these technologies.
In Part 1 of this article we showed how the build of OSGi and Eclipse RCP applications can be automated easily. However, we didn't address testing and quality management issues in any way, although it is a very important aspect of a development project. This tutorial was developed within the scope of the . It shows how OSGi bundles can be tested and how the tests can be automated and integrated in an existing Maven build environment.
In the last two articles we showed how single bundles can be built using Maven and how bundles can be tested inside of the OSGi Environment. For the delivery, the bundles have to be composed in a complete product. The build of such a product, in the best case, is a part of the existing Maven build-process. In this article we describe such a solution.