Author: msorokin Date: 2008-04-21 12:21:55 -0400 (Mon, 21 Apr 2008) New Revision: 8028 Modified: trunk/docs/migrationguide/en/src/main/docbook/included/calendarDate.xml trunk/docs/migrationguide/en/src/main/docbook/included/datascrollerFor.xml trunk/docs/migrationguide/en/src/main/docbook/included/datascrollerPaired.xml trunk/docs/migrationguide/en/src/main/docbook/included/explicitId.xml Log: http://jira.jboss.com/jira/browse/RF-3048 Language correction Modified: trunk/docs/migrationguide/en/src/main/docbook/included/calendarDate.xml =================================================================== --- trunk/docs/migrationguide/en/src/main/docbook/included/calendarDate.xml 2008-04-21 16:21:30 UTC (rev 8027) +++ trunk/docs/migrationguide/en/src/main/docbook/included/calendarDate.xml 2008-04-21 16:21:55 UTC (rev 8028) @@ -33,7 +33,7 @@ <section> <title>How to reproduce</title> <para> - Put <emphasis role="bold"><property>&lt;a4j:support&gt;</property></emphasis> inside <emphasis role="bold"><property>&lt;rich:calendar&gt;</property></emphasis>. + The described above problem occurs when <emphasis role="bold"><property>&lt;a4j:support&gt;</property></emphasis>is put inside <emphasis role="bold"><property>&lt;rich:calendar&gt;</property></emphasis>. If the <emphasis><property>&quot;event&quot;</property></emphasis> property is &quot;ondateselected&quot; previous value of the <emphasis role="bold"><property>&lt;rich:calendar&gt;</property></emphasis> is stored after selection. </para> @@ -48,10 +48,10 @@ <section> <title>Workarounds</title> <para> - You need <emphasis><property>&quot;onchanged&quot;</property></emphasis> event is fired after any change which causes input to be updated, both date and time. + You need <emphasis><property>&quot;onchanged&quot;</property></emphasis> event to be fired after any change which causes input to be updated, both date and time. </para> <para> - Notice, that + Note, that </para> <itemizedlist> <listitem> Modified: trunk/docs/migrationguide/en/src/main/docbook/included/datascrollerFor.xml =================================================================== --- trunk/docs/migrationguide/en/src/main/docbook/included/datascrollerFor.xml 2008-04-21 16:21:30 UTC (rev 8027) +++ trunk/docs/migrationguide/en/src/main/docbook/included/datascrollerFor.xml 2008-04-21 16:21:55 UTC (rev 8028) @@ -12,8 +12,8 @@ <section> <title>Description</title> <para> - The <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> component&apos;s - <emphasis><property>&quot;for&quot;</property></emphasis> attribute doesn&apos;t allow EL expressions in 3.2.0.GA. + The <emphasis><property>&quot;for&quot;</property></emphasis>attribute of <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> component + doesn&apos;t allow EL expressions in 3.2.0.GA. </para> <para> Custom tags exploiting the ability of the <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> to have dynamic @@ -33,7 +33,7 @@ <section> <title>How to reproduce</title> <para> - Just add the following code, that will not work: + The described above problem occurs if the following code is used: </para> <programlisting role="XML"><![CDATA[... <rich:datascroller for="#{bean.property}"/> @@ -49,7 +49,7 @@ <section> <title>Workarounds</title> <para> - None for no + None, so far. </para> </section> </section> \ No newline at end of file Modified: trunk/docs/migrationguide/en/src/main/docbook/included/datascrollerPaired.xml =================================================================== --- trunk/docs/migrationguide/en/src/main/docbook/included/datascrollerPaired.xml 2008-04-21 16:21:30 UTC (rev 8027) +++ trunk/docs/migrationguide/en/src/main/docbook/included/datascrollerPaired.xml 2008-04-21 16:21:55 UTC (rev 8028) @@ -8,14 +8,14 @@ <keyword>page</keyword> </keywordset> </sectioninfo> - <title>Paired &lt;rich:datascroller&gt; components aren&apos;t work</title> + <title>Paired &lt;rich:datascroller&gt; components do not work</title> <section> <title>Description</title> <para> Two <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> components bound to the same table aren&apos;t synchronized. - Storing data component in session-scoped beans no more saves <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> state. + Having two <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis>components on a page, session-scoped beans saves the data for only one <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> component. It is a common pattern to have 2 <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> components: - the first in header, the second in footer. The first will not work. + the first in the header, the second in the footer. In this case the first one will not work. </para> </section> <section> @@ -36,20 +36,20 @@ <section> <title>How to reproduce</title> <para> - Add 2 <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> components to any table. + The described above problem occurs if 2 <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> components added to any table. </para> </section> <section> <title>Causes</title> <para> - The <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> component is now responsible for managing data table&apos;s scroll state. + The <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> component does not manage the scroll state of a data table. </para> </section> <section> <title>Workarounds</title> <para> - The decision is to use <emphasis><property>&quot;page&quot;</property></emphasis> attribute and bind it to the same property for all + The solution is to use <emphasis><property>&quot;page&quot;</property></emphasis> attribute and bind it to the same property for all <emphasis role="bold"><property>&lt;rich:datascroller&gt;</property></emphasis> components. </para> </section> Modified: trunk/docs/migrationguide/en/src/main/docbook/included/explicitId.xml =================================================================== --- trunk/docs/migrationguide/en/src/main/docbook/included/explicitId.xml 2008-04-21 16:21:30 UTC (rev 8027) +++ trunk/docs/migrationguide/en/src/main/docbook/included/explicitId.xml 2008-04-21 16:21:55 UTC (rev 8028) @@ -11,13 +11,13 @@ <section> <title>Description</title> <para> - Ajax requests stop to work without any errors shown when intensive Ajax traffic is expected. No error or other diagnostic presents. + Ajax requests stop to work without any errors messages displayed, when intensive Ajax traffic is expected. No errors or other messages to detect cause of the defect are shown. </para> </section> <section> <title>How to reproduce</title> <para> - Do not define an <property>id</property> for Ajax command component. + The described above problem occurs if an <property>id</property> for Ajax command component is not defined. </para> <programlisting role="XML"><![CDATA[... <h:form> @@ -33,9 +33,9 @@ <section> <title>Causes</title> <para> - This is a specific of the dynamic id generation of the JSF 1.2 implementation. - In case of simultaneous request processing, the id of the command component becomes <property>out-of-sync</property> - with id of the same component on the page. After that any Ajax requests from the component with old id just do not process. + The problem occurred due to specific usage of the dynamic id generation of the JSF 1.2 implementation. + In case of simultaneous request processing, the id of the command component becomes <property>out-of-sync</property> + with id of the same component on the page. After that any Ajax requests from the component with old id just is no processed. </para> </section>