anchor.diff:  <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
  +===== Starting a Service
   Now that you have recorded the creation of a service during the build phase, you need to record how to start the service at runtime during booting. You do this with a RUNTIME_INIT build step as shown in the `TestProcessor#startRuntimeService` method.
   
   .Starting/Stopping a Non-CDI Service
  
positive.code: `io.quarkus.deployment.builditem.substrate.SubstrateConfigBuildItem`::
  A convenience feature that allows you to control most of the above features from a single build item.
  
  == IDE support tips
  
  === Writing {project-name} extensions in Eclipse
  
  The only particular aspect of writing {project-name} extensions in Eclipse is that APT (Annotation Processing Tool) is required as part of extension builds, which means you need to:
  
  
negative.code:     -Dextensions="resteasy-jsonb"
  ----
  
  ==== Bean Defining Annotations
  The CDI layer processes CDI beans that are either explicitly registered or that it discovers based on bean defining annotations as defined in http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#bean_defining_annotations">[2.5.1. Bean defining annotations]. You can expand this set of annotations to include annotations your extension processes using a `BeanDefiningAnnotationBuildItem` as shown in this `TestProcessor#registerBeanDefinningAnnotations` example:
  
  .Register a Bean Definining Annotation
  