anchor.diff:  
   `org.keycloak.adapters.osgi.undertow.CxfKeycloakAuthHandler` is one of such handlers that's integrating CXF
   engine with Keycloak. Using `org.keycloak.adapters.osgi.PathBasedKeycloakConfigResolver` as Keycloak configuration
  -resolver allows us to configure an endpoing using well known `etc/<context>-keycloak.json`.
  +resolver allows us to configure an endpoint using well known `etc/<context>-keycloak.json`.
   
   because we have two endpoints registered in separate CXF server engine, we need two files:
   
  
positive.code: 
  `mvn:org.jboss.fuse.quickstarts.security/keycloak-httpservice-blueprint/<version>` is an example
  where servlets are still registered using HTTP Service (and its pax-web extension), but using Blueprint
  XML descriptor. The bundle embedds `/WEB-INF/keycloak.json`:
  [source,json,options="nowrap"]
  ----
  {
  
negative.code: === OSGi HTTP Service
  
  The _canonical_ way of using servlets in OSGi environment is to use `org.osgi.service.http.HttpService` specified
  in "102 Http Service Specification" in OSGi Enterprise R6 document.
  However it allows to register only `javax.servlet.Servlet` instances and _resources_ (which are effectively
  resource-service servlets).
  
  