anchor.diff:  
   Examples of Java EE compliant application servers: GlassFish (Oracle, open source, reference implementation of Java EE), WildFly (Red Hat / JBoss, open source), WebSphere AS (IBM)…
   
  -== Running Glassfish
  -* Download and install a local copy of Glassfish (see link:Tools.adoc[Tools]).
  +== Running GlassFish
  +* Download and install a local copy of GlassFish (see link:Tools.adoc[Tools]).
   * Note in particular the important `…/glassfish/bin` and `…/glassfish/domains/domain1/autodeploy` directories.
   * The server is commanded thanks to the `asadmin` command (in the `bin` subfolder). This command is to be run in a terminal.
   * Start the server with `asadmin start-domain`: this starts domain1, the default configured domain.
  
positive.code: === Log
  If you use `System.out.println`, the container will by default redirect the output to the log file. However, this is not the cleanest way to log:
  
  * it does not offer configuration possibilities
  * it does not offer differentiated log levels
  * if you later move the code to a standalone library or application, you will have to refactor all those statements to turn them into proper log statements
  
  
negative.code: = An overview of the GlassFish Java EE application server
  :toc: preamble
  :sectanchors:
  
  This document gives a (rough and incomplete) overview of GlassFish, a Java EE application server. This document may serve as an introduction to application servers in Java EE.
  
  == Application servers
  Java EE defines a http://www.oracle.com/technetwork/java/javaee/tech/index.html[set] of specifications, known as Java Specification Requests (JSR). Application servers have to implement [small]#(parts of)# these standards in order to be compliant with [small]#(a subset of)# Java EE. An important standard among those is the Servlet API, or https://www.jcp.org/en/jsr/detail?id=369[JSR 369].
  