anchor.diff:          <configuration>
             <warName>${project.artifactId}</warName>
   
  -          <!-- Exclude GWT client local classes from the deployment, lest 
  -            classpath scanners such as Hibernate and Weld get confused
  -            when the webapp is bootstrapping. -->
  -          <packagingExcludes>**/client/**/*.class</packagingExcludes>
  +          <!--
  +            List of files to leave out of the .war file:
  +            1. GWT client-only classes confuse Hibernate and Weld's
  +            classpath scanners
  +            2. The existence of log4j.properties interferes with JBoss
  +            Logging configuration
  +           -->
  +          <packagingExcludes>**/client/**/*.class,**/log4j.properties</packagingExcludes>
           </configuration>
         </plugin>
   ---------
  
positive.code: 
    <servlet-mapping>
      <servlet-name>UberFireServlet</servlet-name>
      <url-pattern>/CdiWorkbench/Uberfire.html</url-pattern>
    </servlet-mapping>
  
    <servlet>
  
negative.code: that only make sense in the client environment, such as Widgets and
  JavaScript Native Methods. We'll get to these topics later, but for
  now, just be sure to exclude your client-only classes from the .war
  file. We also omit the log4j.properties file from the .war file
  because it takes over JBoss Logging configuration.
  
  The `<packagingExcludes>` setting accepts a comma-separated list of
  patterns, so if you need to exclude more stuff later on, you can.
  