anchor.diff:  ----
   <1> Produce a `ServiceStartBuildItem` to indicate that this is a service starting step that needs to run before the `StartupEvent` is sent.
   
  -=== Register Resources for Use in Native Image
  +==== Register Resources for Use in Native Image
   Not all configuration or resources can be consumed at build time. If you have classpath resources that the runtime needs to access, you need to inform the build phase that these resources need to be copied into the native image. This is done by producing one or more `SubstrateResourceBuildItem` or `SubstrateResourceBundleBuildItem` in the case of resource bundles. Examples of this are shown in this sample `registerNativeImageReources` build step:
   
   .Registering Resources and ResourceBundles
  
positive.code: This means that metadata is only processed once at build time, which both saves on startup time, and also on memory
  usage as the classes etc that are used for processing are not loaded (or even present) in the runtime JVM.
  
  == Three Phases of Bootstrap and Quarkus Philosophy
  
  There are three distinct bootstrap phases of a Quarkus app:
  
  
negative.code: 
  The testcase for validating that the `RuntimeXmlConfigService` has started can be found in the `testRuntimeXmlConfigService` test of `ConfiguredBeanTest` and `NativeImageIT`.
  
  ==== Startup and Shutdown Events
  The {project-name} container supports startup and shutdown lifecycle events to notify components of the container startup
  and shutdown. There are CDI events fired that components can observe are illustrated in this example:
  
  