anchor.diff:  
   ===== Path Parameters
   
  +Path parameters are dynamic parts of an URL which you typically use to embed details about an addressed
  +resource. With PrettyFaces you had to use EL-like expressions in the pattern part of the mapping to
  +add such parameters. Rewrite parameters are very similar to that.  The only real difference is that 
  +you have to use +\{param\}+ instead of +#\{param\}+ for the parameter. 
  +
   [cols="1a,1a", options="header"]
   |===
   |PrettyFaces
  
positive.code: .bindsTo(PhaseBinding.to(El.property("bean.category"))).after(PhaseId.RESTORE_VIEW))
  ----
  
  
  TODO: describe all the other cases.
  
  ==== PrettyFaces Annotations
  
  
negative.code: )
  |===
  
  In the example show above the parameters will be automatically turned into query parameters with
  the same name as the parameter. This means that you can access the parameter using the standard
  Servlet API:
  
  ----
  request.getParameter("category");
  ----
  
  Instead of using the standard Servlet API to access the parameters, it is often easier
  to use EL-injected path parameters. With PrettyFaces you would simply use an EL expression that
  refers to a bean property for that. PrettyFaces will then automatically inject the path parameter
  value into that bean property.
  
  Rewrite uses a concept called _parameter bindings_ to achieve the same. With Rewrite you can
  _bind_ parameters to bean properties by calling +.where("param").bindsTo(...)+. See the following
  code for an example: 
  
  [cols="1a,1a", options="header"]
  |===
  |PrettyFaces
  