Author: artdaw Date: 2009-01-10 11:10:09 -0500 (Sat, 10 Jan 2009) New Revision: 12200 Added: trunk/docs/migrationguide/en/src/main/docbook/included/immediate.xml Modified: trunk/docs/migrationguide/en/src/main/docbook/master.xml Log: https://jira.jboss.org/jira/browse/RF-3048 - Info about "immediate" attribute behavior was added to the Migration Guide Added: trunk/docs/migrationguide/en/src/main/docbook/included/immediate.xml =================================================================== --- trunk/docs/migrationguide/en/src/main/docbook/included/immediate.xml (rev 0) +++ trunk/docs/migrationguide/en/src/main/docbook/included/immediate.xml 2009-01-10 16:10:09 UTC (rev 12200) @@ -0,0 +1,74 @@ +<?xml version="1.0" encoding="UTF-8"?> +<section id="immediate" role="NotInToc"> + <?dbhtml filename="immediate.html"?> + <sectioninfo> + <keywordset> + <keyword>a4j:support</keyword> + <keyword>immediate</keyword> + <keyword>JSP</keyword> + </keywordset> + </sectioninfo> + <title>Behavior of the &quot;immediate&quot; attribute is changed</title> + <section> + <title>Description</title> + <para> + Since we&apos;ve migrated to the <property>JSF 1.2</property> standard in <property>RichFaces 3.2.0</property> the + <emphasis><property>&quot;immediate&quot;</property></emphasis> attribute works exactly like it should according to the JSF 1.2 specification: + the default ActionListener stops execution after the Apply Request Values phase, so there is no interaction with a model any more. + We could not use the standard JSF API before as soon as we had to support not only JSF 1.2, but JSF 1.1 as well. + We used our own hack that emulated the behavior of the attribute. + This approach had a side effect that allowed interacting with a model but now this side effect is gone. + </para> + </section> + <section> + <title>Links</title> + <itemizedlist> + <listitem> + <para> + <ulink url="http://www.jboss.com/index.html?module=bb&amp;op=viewtopic&... Forum</ulink> + </para> + </listitem> + </itemizedlist> + </section> + <section> + <title>How to reproduce</title> + <programlisting role="XML"><![CDATA[... +<h:form> + <h:inputText id="oneA" value="#{bean.name}" size="8"> + <a4j:support event="onkeyup" reRender="three" immediate="true" focus="oneA" action="#{bean.actionOne}"/> + </h:inputText> + <h:selectBooleanCheckbox id="twoA" value="#{bean.option}"> + <a4j:support event="onclick" reRender="three" immediate="true" focus="twoA" action="#{bean.actionOne}"/> + </h:selectBooleanCheckbox> + <h:commandButton id="go" value="Submit"/> +</h:form> +<h:outputText id="three" value="#{bean.name} #{bean.option}"/> +...]]></programlisting> + </section> + <section> + <title>Causes</title> + <para> + Behavior of the <emphasis><property>&quot;immediate&quot;</property></emphasis> attribute is changed according to to JSF 1.2 specification. + </para> + </section> + + <section> + <title>Workarounds</title> + <para> + The solution includes the following steps: + </para> + <itemizedlist> + <listitem> + <para> + replace <emphasis><property>&quot;immediate&quot;</property></emphasis> attribute with <code>ajaxSingle=&quot;true&quot;</code> + </para> + </listitem> + <listitem> + <para> + add <emphasis><property>&quot;process&quot;</property></emphasis> attribute. + This attribute points to the components that should be processed together with the command component. + </para> + </listitem> + </itemizedlist> + </section> +</section> \ No newline at end of file Modified: trunk/docs/migrationguide/en/src/main/docbook/master.xml =================================================================== --- trunk/docs/migrationguide/en/src/main/docbook/master.xml 2009-01-10 15:02:16 UTC (rev 12199) +++ trunk/docs/migrationguide/en/src/main/docbook/master.xml 2009-01-10 16:10:09 UTC (rev 12200) @@ -16,18 +16,20 @@ <!ENTITY datascrollerFor SYSTEM "included/datascrollerFor.xml"> <!ENTITY ajaxSingleFacets SYSTEM "included/ajaxSingleFacets.xml"> <!ENTITY actionparam SYSTEM "included/actionparam.xml"> + <!ENTITY immediate SYSTEM "included/immediate.xml"> + <!ENTITY fileUploadListener SYSTEM "included/fileUploadListener.xml"> <!ENTITY myfaces SYSTEM "included/myfaces.xml"> - <!ENTITY seamMultipartFilter SYSTEM "included/seamMultipartFilter.xml"> - - - <!ENTITY dataTableAjax SYSTEM "included/dataTableAjax.xml"> + <!ENTITY seamMultipartFilter SYSTEM "included/seamMultipartFilter.xml"> + + <!ENTITY dataTableAjax SYSTEM "included/dataTableAjax.xml"> + ]> <book> <bookinfo> - <title>RichFaces Migration Guide</title> + <title>RichFaces Migration Guide</title> <author> <firstname>Gleb</firstname> <surname>Galkin</surname> @@ -106,6 +108,7 @@ &datascrollerFor; &ajaxSingleFacets; &actionparam; + &immediate; </section> <section id="ThirdPartyFrameworks31to32"> @@ -123,8 +126,8 @@ &myfaces; &seamMultipartFilter; </section> - </chapter> - + </chapter> + <chapter id="RichFacesMigrationIssues32to33" xreflabel="RichFacesMigrationIssues32to33"> <?dbhtml filename="RichFacesMigrationIssues32to33.html"?> <chapterinfo> @@ -133,15 +136,15 @@ <keyword>Migration Guide</keyword> </keywordset> </chapterinfo> - <title>The RichFaces Migration Issues 3.2.x - 3.3.0</title> - <para> + <title>The RichFaces Migration Issues 3.2.x - 3.3.0</title> + <para> This chapter includes only those issues that concern migration from from 3.2.x versions to 3.3.0. Issues, that are related to the new components and other problems are not covered here. However, <ulink url="http://jira.jboss.com/jira/browse/RF">Jira</ulink> contains all issues - and if you can not find your case there, please, feel free to report it. - </para> + and if you can not find your case there, please, feel free to report it. + </para> - + &dataTableAjax; </chapter> </book>