[Myfaces Wiki] Update of "FacesMajor Renderers" by MatthiasWessendorf

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Myfaces Wiki" for change notification.

The following page has been changed by MatthiasWessendorf:
http://wiki.apache.org/myfaces/FacesMajor_Renderers

------------------------------------------------------------------------------
  {{{
    protected void encodeAll(
      FacesContext        context,
-     AdfRenderingContext arc,
+     RenderingContext    arc,
      UIComponent         component,
      FacesBean           bean) throws IOException
  }}}
@@ -27, +27 @@

  {{{
    protected void encodeBegin(
      FacesContext        context,
-     AdfRenderingContext arc,
+     RenderingContext    arc,
      UIComponent         component,
      FacesBean           bean) throws IOException
    protected void encodeEnd(
      FacesContext        context,
-     AdfRenderingContext arc,
+     RenderingContext    arc,
      UIComponent         component,
      FacesBean           bean) throws IOException
  }}}
@@ -78, +78 @@

  
  === Replacements for old UIX functionality ===
  
- AdfRenderingContext replaces most of the RenderingContext functionality.
+ AdfRenderingContext replaces most of the UIXRenderingContext functionality.
-  * AdfRenderingContext can be retrieved as a thread-local with getCurrentInstance().
+  * RenderingContext can be retrieved as a thread-local with getCurrentInstance().
-  * AdfRenderingContext.getProperties() returns a Map for rendering properties.
+  * RenderingContext.getProperties() returns a Map for rendering properties.
  
- One special thing about AdfRenderingContext.getProperties():  if you store an old RenderingContext property, using the MARLIN_NAMESPACE namespace, it actually goes into the AdfRenderingContext properties Map!  So, as long as you use exactly the same key, old- and new-style code can communicate.
+ One special thing about RenderingContext.getProperties():  if you store an old UIXRenderingContext property, using the MARLIN_NAMESPACE namespace, it actually goes into the RenderingContext properties Map!  So, as long as you use exactly the same key, old- and new-style code can communicate.
  
  Instead of providing PDA or BLAF renderers that just subclass a few things, lean on Skin properties.  For example, when deciding whether to show the last "breadCrumb"/"menuPath" item, we now use a Skin property.