anchor.diff:  This behaviour can be changed by setting the servlet initialization parameter `org.jboss.weld.environment.servlet.archive.isolation` to false.
   In this case, Weld will use a "flat" deployment structure - all bean classes share the same bean archive and all beans.xml descriptors are automatically merged into one. Thus alternatives, interceptors and decorators selected/enabled for a bean archive will be enabled for the whole application.
   
  -NOTE: Bean archive isolation is supported (and enabled by default) from version 2.2.5.Final. Previous versions only operated with the "flat" deployment structure.   
  +NOTE: Bean archive isolation is supported (and enabled by default) from version 2.2.5.Final. Previous versions only operated with the "flat" deployment structure.
   
   ==== Implicit Bean Archive Support
   
  -CDI 1.1 introduced the bean discovery mode of `annotated` used for implicit bean archives (see also <<packaging-and-deployment>>). 
  -This mode may bring additional overhead during container bootstrap. Therefore, Weld Servlet supports the use of https://github.com/wildfly/jandex[Jandex] bytecode scanning library to speed up the scanning process. Simply put the http://search.maven.org/#search|gav|1|g%3A%22org.jboss%22%20AND%20a%3A%22jandex%22[jandex.jar] on the classpath. 
  +CDI 1.1 introduced the bean discovery mode of `annotated` used for implicit bean archives (see also <<packaging-and-deployment>>).
  +This mode may bring additional overhead during container bootstrap. Therefore, Weld Servlet supports the use of https://github.com/wildfly/jandex[Jandex] bytecode scanning library to speed up the scanning process. Simply put the http://search.maven.org/#search|gav|1|g%3A%22org.jboss%22%20AND%20a%3A%22jandex%22[jandex.jar] on the classpath.
   If Jandex is not found on the classpath Weld will use the Java Reflection as a fallback.
   
  -In general, an implicit bean archive does not have to contain a beans.xml descriptor. However, such a bean archive is not supported by Weld Servlet, i.e. it's excluded from discovery.  
  +In general, an implicit bean archive does not have to contain a beans.xml descriptor. However, such a bean archive is not supported by Weld Servlet, i.e. it's excluded from discovery.
   
   NOTE: The bean discovery mode of `annotated` is supported from version 2.2.5.Final. Previous versions processed implicit bean archives in the same way as explicit bean archives.
   
  
positive.code: 
  ==== Tomcat
  
  Since version 2.2.0.Final only Tomcat 7 and 8 are supported.
  
  Tomcat has a read-only JNDI, so Weld can't automatically bind the
  BeanManager extension SPI. To bind the BeanManager into JNDI, you should
  populate `META-INF/context.xml` in the web root with the following
  
negative.code: Jetty only allows you to bind entries to `java:comp/env`, so the
  BeanManager will be available at `java:comp/env/BeanManager`.
  
  ===== Embedded Jetty
  
  When starting embedded Jetty programmatically from the main method it is necessary
  to register Weld's listener:
  
  [source.JAVA, java]
  -------------------------------------------------------------
  public class Main {
  
      public static void main(String[] args) throws Exception {
          Server jetty = new Server(8080);
          WebAppContext context = new WebAppContext();
          context.setContextPath("/");
          context.setResourceBase("src/main/resources");
          jetty.setHandler(context);
          context.addServlet(HelloWorldServlet.class, "/*");
  
          context.addEventListener(new Listener()); # <1>
  
          jetty.start();
          jetty.join();
      }
  
      public static class HelloWorldServlet extends HttpServlet {
  
          @Inject BeanManager manager;
  
          protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {
              resp.setContentType("text/plain");
              resp.getWriter().append("Hello from " + manager);
          }
      }
  }
  -------------------------------------------------------------
  <1> Weld's `org.jboss.weld.environment.servlet.Listener` registered programmatically:
  
  ==== Bean Archive Isolation
  
  