anchor.diff:      return repositoryService.persist(SimpleObject.ofName(name));
   }
   ----
  +
  +The `@Name` annotation on the action parameter is actually a meta-annotation, meaning that a number of additional semantics (length, layout, validation etc.) are inferred.
   
   TIP: Policies such as modal or sidebar can be specified per action, or globally in `application.yml` file.
   
  
positive.code: 
      public static class ActionDomainEvent<S> extends
      org.apache.isis.applib.events.domain.ActionDomainEvent<S> {}
  }
  ----
  <1> This module has no dependencies.
  If there were, these would be expressed in terms of module classes (each being a Spring `@Configuration`)
  <2> specifies this class' package as a root to scan for Spring link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Component.html[@Component]s.
  <3> Optionally, modules can implement the testing's `ModuleWithFixtures` interface.
  Through this, they can provide a fixture script which can be used to teardown all entities that are "owned" by the module.
  Since the module dependency graph is known, this allows all data to be removed, useful for prototyping and sometimes for integration tests.
  <4> The actions for the domain objects and domain services all emit domain events, ultimately inheriting from xref:refguide:applib-cm:classes/domainevent/ActionDomainEvent.adoc[ActionDomainEvent].
  By convention, this inheritance hierarchy includes classes defined at the module level.
  This then allows subscribes to subscribe to all actions emitted by anything within the module. +
  Events can also be emitted for xref:refguide:applib-cm:classes/domainevent/PropertyDomainEvent.adoc[properties] and xref:refguide:applib-cm:classes/domainevent/CollectionDomainEvent.adoc[collections].
  
  The scanning mechanism is leveraged by Apache Isis to pick up three types of classes:
  
  
negative.code: package domainapp.modules.simple;
  ... imports omitted ...
  @Configuration
  @Import({})                                                                 //<!--1-->
  @ComponentScan                                                              //<!--2-->
  public class SimpleModule
                  implements ModuleWithFixtures {                             //<!--3-->
  
      @Override
      public FixtureScript getTeardownFixture() {
  