anchor.diff:  metamodel, but I don’t use that as it hinders compatibility of the
   project with other IDEs.)
   
  -[[jsf-best-practices]]
  -JSF best practices
  -~~~~~~~~~~~~~~~~~~
  -
  -[[multiple-field-validation]]
  -Multiple field validation
  -^^^^^^^^^^^^^^^^^^^^^^^^^
  -
  +== 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
  
positive.code: :toc:
  :sectanchors:
  
  = Samples
  
  Here are some samples about Java EE technologies (JPA in Java SE is
  covered as well). They serve two purposes:
  
  * give a head start to someone who wants a correctly configured, working
  project as a basis for work; and
  * support discussion around “best” practices by showing their
  applications in concrete, simple cases.
  
  Scroll down for the discussion about (what I consider to be) the best
  practices.
  
  [[common-features]]
  Common features
  ~~~~~~~~~~~~~~~
  
  All projects use Maven.
  
  [[javaee-inject-produces-servlets]]
  JavaEE-Inject-Produces-Servlets
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  Shows usage of CDI (Injection of managed beans) and producers together
  with simple servlets. Note that you do not need to understand producers
  to be able to use CDI, so do not look there yet if you just want to know
  
negative.code: proposal
  http://balusc.omnifaces.org/2007/12/validator-for-multiple-fields.html[here].
  
  == 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 plus logback for Java SE projects.
  