anchor.diff:  <1> We consume a ShutdownContextBuildItem to register the service shutdown.
   <2> We consume the previously initialized service captured in `RuntimeServiceBuildItem`.
   <3> Call the runtime template to record the service start invocation.
  -<4> Runtime template retrieves the service instance reference and calls it's `startService` method.
  +<4> Runtime template retrieves the service instance reference and calls its `startService` method.
   <5> Runtime template registers an invocation of the service instance `stopService` method with the {project-name} `ShutdownContext`.
   
   The code for the `RuntimeXmlConfigService` can be viewed here:
  
positive.code: }
  ----
  <1> Call into the runtime template to record the creation of the service.
  <2> Using the parsed `XmlConfig` instance, create a instance of `RuntimeXmlConfigService` and wrap it in a `RuntimeValue`. Use a `RuntimeValue` wrapper for non-interface objects that are non-proxiable.
  <3> Wrap the return service value in a `RuntimeServiceBuildItem` for use in a RUNTIME_INIT build step that will start the service.
  
  ==== Starting a Service
  
negative.code: ====
  
  === Scanning Deployments Using Jandex
  If your extension defines annotations or interfaces that mark beans needing to be processed, you can locate these beans using the Jandex API, a Java annotation indexer and offline reflection library. The following `TestProcessor#scanForBeans` method shows how to find the beans annotated with our `@TestAnnotation` that also implement the `IConfigConsumer` interface:
  
  .Example Jandex Usage
  [source,java]
  ----
      static DotName TEST_ANNOTATION = DotName.createSimple(TestAnnotation.class.getName());
  