Why use a Servlet Bridge?
Suppose that you want the servlets of your application to be dynamic but you don’t want to use the OSGi HTTP Service for one of the countless reasons like: No real support for this service, the service itself is not as stable as well known Servlet Containers like Apache Tomcat, you don’t want to be at the risk of finding many missing features along the way or many of the other risks associated with an immature technology. At times like this, you might want to use the new dynamic technology (the OSGi-based application) alongside the mature and stable technology (be it a Servlet Container or an Application Server) not the dynamic technology completely replacing the mature technology. Servlet Bridges provide you with such option by allowing the non-osgi Web Application delegate HTTP requests to OSGi Servlet Services provided by an OSGi-based application.
