anchor.diff:  </jboss-deployment-structure>
   ----
   
  -Because of JBoss Modules' `ClassLoader` magic, you'll likely need to provide the `ClassLoader` of your classes <<solverConfigurationByXML,during the SolverFactory creation>>,
  -so it can find the classpath resources (such as the solver config, score DRL's and domain classes) in your jars.
  +
  +[[integrationWithSpringBoot]]
  +=== Spring Boot
  +
  +Normally Planner just works on Spring Boot, simply add the `optaplanner-core` dependency.
  +If it has trouble finding classpath resources (such as the solver config, score DRL's and domain classes),
  +provide the `ClassLoader` of your classes <<solverConfigurationByXML,during the SolverFactory creation>>.
   
   
   [[integrationWithOSGi]]
  
positive.code: .. Remove `optaplanner-core-${version}.jar` and all its direct and transitive dependency jars from the `WEB-INF/lib` directory in the `war` file.
  .. Create the file `jboss-deployment-structure.xml` in the `WEB-INF/lib` directory. Give it this content:
  +
  
  [source,xml,options="nowrap"]
  ----
  <?xml version="1.0" encoding="UTF-8" ?>
  
negative.code: The `optaplanner-core` jar includes OSGi metadata in its `MANIFEST.MF` file to function properly in an OSGi environment too.
  Furthermore, the maven artifact `kie-karaf-features` contains a `features.xml` file that supports the OSGi-feature ``optaplanner-engine``.
  
  Because of the OSGi's `ClassLoader` magic, provide the `ClassLoader` of your classes <<solverConfigurationByXML,during the SolverFactory creation>>,
  so it can find the classpath resources (such as the solver config, score DRL's and domain classes) in your jars.
  
  [NOTE]
  