[Myfaces Wiki] Trivial Update of "FAQ" by SimonKitching

[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 SimonKitching:
http://wiki.apache.org/myfaces/FAQ

The comment on the change is:
Minor tidyups

------------------------------------------------------------------------------
  pretty output. However this option was never well supported as it requires support from every renderer in order to work. This feature
  may be removed from future versions of !MyFaces.
  
- === What do version numbers mean for the Tomahawk library? ===
+ === What do version numbers mean for the MyFaces Core and Tomahawk releases? ===
  
- Tomahawk uses 3-part version numbers, eg 1.1.1. However this value is different from the usual version numbering. The first two digits indicate
+ !MyFaces Core uses 3-part version numbers, eg 1.1.1. However this value is different from the usual version numbering. The first two digits indicate
+ which JSF specification the release is an implementation of. Because the binary api for a JSF specification does not change, two releases with the
+ same first two digits are guaranteed to be binary compatible; all existing code using JSF-specified features will continue to work as previously
- which JSF specification the release is compatible with. And '''importantly''' the last digit is '''not''' a "patch version", simply a release count.
- There is no guarantee that release a.b.x is binary-compatible with a.b.y; effectively every release of Tomahawk may be binary incompatible
- with the previous release, potentially requiring changes in JSP files that use tomahawk components and changes to custom components that
- use tomahawk classes. The !MyFaces project does not provide any "maintenance" releases of the Tomahawk library; if there is a bug in the version
- you are using the only option is to upgrade to the next release and change your application to match.
- 
- For releases of the !MyFaces JSF implementation (myfaces-api and myfaces-impl jars), a change to the third digit of the release number does
- indicate a binary-compatible release, as the JSF specification number has not changed. All code using JSF-specified features will continue
- to work as previously (unless the previous behaviour was buggy).
+ (unless the previous behaviour was buggy).
+ 
+ The Tomahawk library also uses the same format of version number. However as the JSF 1.2 specification is backwards-compatible with the JSF 1.1 specification,
+ Tomahawk releases with version numbers 1.1.x also work fine with JSF 1.2. Note however that Tomahawk releases are not guaranteed to be binary compatible with
+ the previous Tomahawk release; an increment in the third digit is simply a release-count and '''not''' a "patch version". There are no releases of Tomahawk
+ that are simply "bugfix" releases
+ 
+ Note in addition that Tomahawk releases are only tested with the latest versions of the !MyFaces and Sun JSF implementations available at the time of release.
+ Success with other versions of these libraries, or with other libraries is likely but not guaranteed. In particular, when running early releases of Tomahawk
+ with !MyFaces Core, the versions used generally had to match exactly (due to the way the "shared" library was used). This has since been improved, and recent
+ Tomahawk releases have a good chance of working with multiple versions of !MyFaces Core.
  
  === Why isn't DataModel serializable? ===
  
@@ -158, +162 @@

  === Why are my dates displaying the wrong day/time? ===
  [#Date permlink]
  
- The Sun JSF spec requires that date->string converters default to using the standard UTC (aka GMT) timezone.
+ The JSF specification requires that date->string converters default to using the standard UTC (aka GMT) timezone.
  
  Note that !MyFaces releases 1.1.0 and earlier did not comply with the JSF spec; they defaulted to using the
  timezone of the server.
@@ -173, +177 @@

  }}}
  where #{bean.timeZone} returns either a string id, or a !TimeZone instance.
  
- The MyFaces sandbox contains a custom converter tag which is like f:convertDateTime, but defaults to
+ The !MyFaces sandbox contains a custom converter tag which is like f:convertDateTime, but defaults to
  using the timezone of the server:
  {{{
      <s:convertDateTime/>
@@ -189, +193 @@

  See AccessingOneManagedBeanFromAnother
  
  === Handling forward references to components in JSP pages ===
+ 
+ Note: this information applies only to projects using JSF 1.1 and JSP. Projects using
+ either JSF 1.2 or Facelets can ignore this section.
  
  In some cases, a component in a JSP page needs to reference another component by id.
  One common example is the tomahawk t:dataScroller component. This is fine when the