anchor.diff:  proposal
   http://balusc.omnifaces.org/2007/12/validator-for-multiple-fields.html[here].
   
  -[[logging-best-practices]]
  -Logging best practices
  -~~~~~~~~~~~~~~~~~~~~~~
  -
  -[[framework]]
  -Framework
  -^^^^^^^^^
  -
  +== Logging best practices
  +=== [[logging-choice]]Framework
   One of the PITA in Java world is the multiplicity of logging framework.
  -My personal choice is to go for JUL for Java EE projects and SLF4J +
  -logback for Java SE projects.
  +My personal choice is to go for JUL for Java EE projects and SLF4J plus logback for Java SE projects.
  
positive.code: http://download.oracle.com/otn-pub/jcp/servlet-3_1-fr-eval-spec/servlet-3_1-final.pdf[spec],
  A.7.6 and 10.13).]
  
  [[jpa-best-practices]]
  JPA best practices
  ~~~~~~~~~~~~~~~~~~
  
  [[use-delimited-identifiers]]
  Use delimited identifiers
  ^^^^^^^^^^^^^^^^^^^^^^^^^
  
  Tell JPA to use delimited identifiers (see the object/relational xml
  mapping file, `orm.xml`, in the JPA samples). (See JSR 338 JPA 2.1
  link:[spec], section 2.13.) JPA will then “delimit” (quote) all SQL
  
negative.code: metamodel, but I don’t use that as it hinders compatibility of the
  project with other IDEs.)
  
  == JSF best practices
  === [[multifield]]Multiple field validation
  Sometimes the validation logic requires knowledge of the value of
  multiple fields. (Example: required `start` ≤ `end`, where `start` and
  `end` are two request parameters.) In such case I consider the usual JSF
  