anchor.diff:  import io.quarkus.runtime.ShutdownEvent;
   import io.quarkus.runtime.StartupEvent;
   
  -puclic class SomeBean {
  +public class SomeBean {
       /**
        * Called when the runtime has started
        * @param event
  
positive.code: }
  ----
  <1> Observe a `StartupEvent` to be notified the runtime has started.
  <2> Observe a 'ShutdownEvent` to be notified when the runtime is going to shutdown.
  
  What is the relevance of startup and shutdown events for extension authors? We have already seen the use of a `ShutdownContext`
  to register a callback to perform shutdown tasks in the <<Starting a Service>> section. These shutdown tasks would be called
  
negative.code: 
  An extension registers this substitution by producing an `ObjectSubstitutionBuildItem` as shown in this `TestProcessor#loadDSAPublicKey` fragment:
  
  .Registering an Object Substitution
  [source,java]
  ----
      @BuildStep
  