[jboss-cvs] JBossAS SVN: r90869 - projects/docs/enterprise/4.3.5.1/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jul 6 18:32:05 EDT 2009
Author: irooskov at redhat.com
Date: 2009-07-06 18:32:05 -0400 (Mon, 06 Jul 2009)
New Revision: 90869
Modified:
projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml
Log:
updated release notes with new JIRA added pertaining to the updating of components
Modified: projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml 2009-07-06 21:55:55 UTC (rev 90868)
+++ projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml 2009-07-06 22:32:05 UTC (rev 90869)
@@ -254,7 +254,7 @@
</para>
</formalpara>
<programlisting>
-up2date jbossas jboss-seam2 rh-eap-docs jboss-profiler
+up2date jbossas jboss-seam2 rh-eap-docs
</programlisting>
<formalpara>
<title>
@@ -265,7 +265,7 @@
</para>
</formalpara>
<programlisting>
-yum update jbossas jboss-seam2 rh-eap-docs jboss-profiler
+yum update jbossas jboss-seam2 rh-eap-docs
</programlisting>
<important>
<para>
@@ -365,7 +365,7 @@
<listitem>
<para>
Run the following command:
- <screen><command>up2date jbossas jboss-seam2 rh-eap-docs jboss-profiler</command></screen>
+ <screen><command>up2date jbossas jboss-seam2 rh-eap-docs</command></screen>
</para>
</listitem>
</itemizedlist>
@@ -397,11 +397,11 @@
<listitem>
<para>
Run the following command:
- <screen><command>yum install jbossas jboss-seam2 rh-eap-docs jboss-profiler</command></screen>
+ <screen><command>yum install jbossas jboss-seam2 rh-eap-docs</command></screen>
</para>
<note>
<para>
- Installation of the documentation (rh-eap-docs) and the log-based event profiler (jboss-profiler) are optional but recommended as these will assist you in understanding and troubleshooting the JBoss Enterprise Application Platform.
+ Installation of the documentation (rh-eap-docs) is optional but recommended as this will assist you in understanding and troubleshooting the JBoss Enterprise Application Platform.
</para>
</note>
</listitem>
@@ -566,17 +566,17 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1926">JBPAPP-1926</ulink>: The <classname>seam-gen</classname> test would fail if a space existed within the path to the project. Since this is a limitation of Embedded JBoss, the <filename>build-scripts/build.xml</filename>, <filename>build-scripts/build-war.xml</filename> and <filename>seam-gen/build.xml</filename> files have been udpated to generate a message to the user that the tests cannot be executed because of a space in the path to the project.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1926">JBPAPP-1926</ulink>: The <classname>seam-gen</classname> test would fail if a space existed within the path to the project. Since this is a limitation of Embedded JBoss, the <filename>build-scripts/build.xml</filename>, <filename>build-scripts/build-war.xml</filename> and <filename>seam-gen/build.xml</filename> files have been updated to generate a message to the user that the tests cannot be executed because of a space in the path to the project.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1925">JBPAPP-1925</ulink>: The number of checks to see if jBPM is installed in the <classname>BusinessProcessContext</classname> was excessive. This number has been reduced for this release by modifying the <classname>BusinessProcessContext</classname> class to test only once with the <methodname>BusinessProcessContext</methodname> method. The <classname>Lifecycle</classname> and <classname>TestLifecycle</classname> classes have also been updated to now test the application context at the beginning of the <methodname>beginTest</methodname> method instead of the final opperation.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1925">JBPAPP-1925</ulink>: The number of checks to see if jBPM is installed in the <classname>BusinessProcessContext</classname> was excessive. This number has been reduced for this release by modifying the <classname>BusinessProcessContext</classname> class to test only once with the <methodname>BusinessProcessContext</methodname> method. The <classname>Lifecycle</classname> and <classname>TestLifecycle</classname> classes have also been updated to now test the application context at the beginning of the <methodname>beginTest</methodname> method instead of the final operation.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1923">JBPAPP-1923</ulink>: In order to improve <classname>SeamELResolver</classname> and component lookup performance the <classname>ScopeType</classname> class has been updated to move <property>String</property> concatination to it's own method and for the <methodname>getPrefix</methodname> method within the <classname>PageContext</class> to return a <varname>PAGE_CONTEXT_PREFIX</varname> type.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1923">JBPAPP-1923</ulink>: In order to improve <classname>SeamELResolver</classname> and component lookup performance the <classname>ScopeType</classname> class has been updated to move <property>String</property> concatenation to it's own method and for the <methodname>getPrefix</methodname> method within the <classname>PageContext</class> to return a <varname>PAGE_CONTEXT_PREFIX</varname> type.
</para>
</listitem>
<listitem>
@@ -591,7 +591,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1914">JBPAPP-1914</ulink>: It was possible to leak details (real name and username) of a previously logged in user to an un-authenticated user in the booking example. This is because the <property>user</property> field on the SLSB authenticator was not cleared on every log in attempt. If an unauthenticated user obtained a previously used SLSB, the <property>user</property> field would then already be set to another users details, and if their login attempt faied then the other users details would be returned to the session. If this user then clicked the <property>create account</property> button, the username and real name fields would be pre-filled with the other user's details.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1914">JBPAPP-1914</ulink>: It was possible to leak details (real name and username) of a previously logged in user to an un-authenticated user in the booking example. This is because the <property>user</property> field on the SLSB authenticator was not cleared on every log in attempt. If an unauthenticated user obtained a previously used SLSB, the <property>user</property> field would then already be set to another users details, and if their login attempt failed then the other users details would be returned to the session. If this user then clicked the <property>create account</property> button, the username and real name fields would be pre-filled with the other user's details.
</para>
<para>
To fix this security vulnerability the <classname>AuthenticatorAction</classname> class of the booking example has been fixed by note requiring any inwards information. This has been achieved by adding and setting the <property>@In(required=false)</property> property correctly.
@@ -641,11 +641,21 @@
</listitem>
<listitem>
<para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1906">JBPAPP-1906</ulink>: The Selenium RC component of the Feature Pack distribution has been upgraded to version 1.0-beta2. This upgrade has altered the default behavior of how the Internet Explorer and FireFox web browsers are launched to provide an improved user experience and corrected FireFox 3 compatibility. An improved XPath library has also been included for browsers that do not contain XPath natively, along with the addition of the UI-Element that allows for a map file to be written in javascript and provides a new abstraction layer.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1905">JBPAPP-1905</ulink>: The DVD Store example application contains non-Latin characters. These characters were being encoded twice: once when they were imported into the database (via <filename>import.sql</filename>), and a second time during rendering. This resulted in HTML entities (for example, &nbsp;) appearing on a rendered page in a browser. All HTML has been removed from the <filename>import.sql</filename> file, and the entities are now rendered correctly in a browser.
</para>
</listitem>
<listitem>
<para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1903">JBPAPP-1903</ulink>: The JBoss EL component has been upgraded to version 1.0_02.CR3, fixing a cleanup thread and memory leak that existed in the Reference Utility. This has been achieved by the addition of the <classname>JBossELReferenceCache</classname> class that provides the initiation and termination of the Reflection Utility, ensuring that no application leak occurs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1883">JBPAPP-1883</ulink>: The SOA Platform shipped multiple <filename>jbpm-jpdl.jar</filename> files. Because more than one jPDL was available, a <exceptionname>ClassCastException</exceptionname> occurred when <literal>EsbNotifier</literal> or <literal>EsbActionHandler</literal> were called in an application. <literal>ManagedJbpmContext</literal> now closes the jBPM context before the transaction terminates, and creates a new context for subsequent transactions, so that multiple instances of jBPM do not occur.
</para>
</listitem>
More information about the jboss-cvs-commits
mailing list