In the previous chapter we looked at the Eclipse/OSGi architecture and how it works, and then how it relates to the underlying infrastructure of WAS. While WAS is layered, pretty much like every other piece of software on the market, it is also componentized and split into subsystems, that is, systems of components. The components are defined using the Eclipse and OSGi technologies described in the previous chapter, with extensions, extension points, and services accessed via the underlying Eclipse/OSGi registries. This is, however, just one view of the architecture that allows WAS dynamic extensibility. There are other views or perspectives that are just as valid.


Control Region Extension Point Object Request Broker Implementation Class Thread Pool 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Colin Renouf 2009

Personalised recommendations