anchor.diff:  }
   ----
   <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.
  +<2> Using the parsed `XmlConfig` instance, create an 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
  
positive.code: <5> Save the bean class in a `TestBeanBuildItem` for use in a latter RUNTIME_INIT build step that will interact with the bean instances.
  
  === Interacting With Extension Beans
  You can use the `io.quarkus.arc.runtime.BeanContainer` interface to interace with your extension beans. The following `configureBeans` methods illustrate interacting with the beans scanned for in the previous section:
  
  .Using CDI BeanContainer Interface
  [source,java]
  
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());
  