From richfaces-svn-commits at lists.jboss.org Thu Oct 4 07:09:50 2007 Content-Type: multipart/mixed; boundary="===============2905771400308986946==" MIME-Version: 1.0 From: richfaces-svn-commits at lists.jboss.org To: richfaces-svn-commits at lists.jboss.org Subject: [richfaces-svn-commits] JBoss Rich Faces SVN: r3254 - trunk/docs/userguide/en/src/main/docbook/modules. Date: Thu, 04 Oct 2007 07:09:50 -0400 Message-ID: --===============2905771400308986946== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: vkorluzhenko Date: 2007-10-04 07:09:50 -0400 (Thu, 04 Oct 2007) New Revision: 3254 Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml Log: http://jira.jboss.com/jira/browse/RF-1049 - improved description Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover= .xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2= 007-10-04 10:56:28 UTC (rev 3253) +++ trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2= 007-10-04 11:09:50 UTC (rev 3254) @@ -268,19 +268,14 @@
Filter Configuration - RichFaces uses filters for a correction of code received on an A= jax request. In case of a + RichFaces uses a filter for a correction of code received on an = Ajax request. In case of a "regular" JSF request a browser makes correction independe= ntly. In case of - Ajax request in order to prevent layout destruction it's needed= to use filters, + Ajax request in order to prevent layout destruction it's needed= to use a filter, because a received code could differ from a code validated by a brow= ser and a browser doesn't make any corrections. = - In RichFaces 3.1 filter configuration becomes more flexible. The= re is no need to select - between two different filters (Filter or Fast Filter) for the whole = application as it was - earlier. Now it's possible to configure different filters for d= ifferent sets of pages - for the same application. The previous variants of configuration for= the Filter and Fast - Filter are also available for backward compatibility (examples are p= laced below). + An example of how to set a Filter in a web.xml file of your appl= ication is placed below. = - The first one: Example: @@ -294,21 +289,15 @@ ... ]]> = - The second one: - - Example: - + + Note:Fast Filter is deprecated and available only for= backward compatibility + with previous RichFaces versions. Fast Filter usage isn't recom= ended, because there + is another way to use its functionality by means of Neko filter type. = - - RichFaces FastFilter - richfaces - org.ajax4jsf.FastFilter - -... -]]> + In RichFaces 3.1 filter configuration becomes more flexible. It&= apos;s possible to + configure different filters for different sets of pages for the same= application. = - In RichFaces 3.1 the possible filter types are: + The possible filter types are: = @@ -316,22 +305,21 @@ = - Tidy filter corresponds to the former "Filter" and it'= s based on the - Tidy parser. This filter is recommended for applications with compli= cated or non-standard - markup when all necessary code corrections are made by the filter wh= en a response comes from - the server. + "TIDY" filter type based on the Tidy parser. This filt= er is recommended for applications with + complicated or non-standard markup when all necessary code correctio= ns are made by the filter + when a response comes from the server. = - NEKO + NEKO = - Neko filter corresponds to the former "Fast Filter" an= d it's based on - the Neko parser. In case of using this filter code isn't strict= ly verified. Use this - one if you are sure that your application markup is really strict fo= r this filter. Otherwise - it could cause lot's of errors and corrupt a layout as a result= . This filter - considerably accelerates all Ajax requests processing. + "NEKO" filter type corresponds to the former "Fas= t Filter" and it's + based on the Neko parser. In case of using this filter code isn&apos= ;t strictly verified. + Use this one if you are sure that your application markup is really = strict for this filter. + Otherwise it could cause lot's of errors and corrupt a layout a= s a result. This + filter considerably accelerates all Ajax requests processing. = @@ -380,29 +368,25 @@ = The example shows that ORDER parameter defines the order in whic= h particular filter types are used for pages code correction. - First of all "NONE" value is specified for the filter= . Then 2 different + First of all "NONE" type is specified for the filter.= Then two different sets of pages are defined for which two filter types (NONE and NEKO)= are used correspondingly. If a page relates to the first set that is defined in the following = way: = /pages/performance\= .xhtml,/pages/default.*\.xhtml, ]]> = - it's not corrected, because filter value for this page is = defined as + it's not corrected, because filter type for this page is d= efined as "NONE". If a page is not from the first set, then "NE= KO" - value is set. + type is set. If a page relates to the second set that is defined in the follo= wing way: = /pages/repeat\.xhtm= l, ]]> = - then Neko filter is used for correction. If it's not relate= d to the second set, - "TIDY" value is set for the filter (Tidy filter is used fo= r code + then "NEKO" filter type is used for correction. If it&= apos;s not related to the second set, + "TIDY" type is set for the filter ("TIDY" filter= type is used for code correction). = - - Note: It's possible to configure different types= (NONE, NEKO and TIDY) - only for Filter. Fast Filter doesn't support this functionality= . It's - available for backward compatibility with previous RichFaces version= s.
= = Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml 2007-10-04 = 10:56:28 UTC (rev 3253) +++ trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml 2007-10-04 = 11:09:50 UTC (rev 3254) @@ -691,7 +691,7 @@ To avoid exception, don't forget that the compo= nent stores beans in serialized view, but your bean should implement ja= va.io.Serializable. -
+
Why form isn't submitted or setter isn't = called after AJAX --===============2905771400308986946==--