anchor.diff:  </web-app>
   -----------------------------------------------------------------------------------------------------------
   
  -NOTE: An integrator is allowed to specify an alternative way of enabling the development mode.
  +NOTE: An integrator is allowed to specify an alternative way of enabling the development mode. See for example https://docs.jboss.org/author/display/WFLY/CDI+Reference#CDIReference-Developmentmode[WildFly Documentation].
   
   ==== Weld SE
   
  
positive.code: java -cp myCoolApp.jar -Dorg.jboss.weld.development=true com.foo.MyMain
  -----------------------------------------------------------------------------------------------------------
  
  or use the `Weld.property()` method:
  
  [source.JAVA, java]
  -----------------------------------------------------------------
  org.jboss.weld.environment.se.Weld;
  
  public static void main(String[] args) {
     Weld weld = new Weld().property("org.jboss.weld.development", true);
     try (WeldContainer container = weld.initialize()) {
        ...
     }
  }
  
negative.code: [[probe]]
  ==== Probe
  
  This tool allows you to inspect the application CDI components at runtime.
  There is a default UI - HTML client (single-page application), which is only available in web applications.
  Just point your browser to `protocol://host:port/webappContextPath/weld-probe`, e.g. `http://localhost:8080/weld-numberguess/weld-probe`.
  However, it's also posible to obtain the JSON data through the REST API, eventually (if <<config-dev-mode,JMX support is enabled>>) through the MXBean of name `org.jboss.weld.probe:type=JsonData,context=ID` where ID should be replaced with an idenfitier of an application.
  Right now, Probe integration is provided for WildFly, Tomcat and Jetty (Weld Servlet), and Weld SE.
  
  TIP: There are some configuration properties which allow to tune or disable Probe features, e.g. to restrict the set of components which will be monitored. See also <<config-dev-mode>>.
  
  