[jboss-cvs] JBossAS SVN: r90606 - projects/docs/enterprise/4.3.5.1/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Jun 26 00:31:11 EDT 2009
Author: irooskov at redhat.com
Date: 2009-06-26 00:31:10 -0400 (Fri, 26 Jun 2009)
New Revision: 90606
Modified:
projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml
Log:
updated release notes with new JIRA
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-06-25 22:57:06 UTC (rev 90605)
+++ projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml 2009-06-26 04:31:10 UTC (rev 90606)
@@ -96,8 +96,8 @@
<para>
Listed in this section are the components which were included in the previous Feature Pack and have been updated within this release. This information is included within the release notes in order to assist with the decision of upgrading to this release.
</para>
- <!-- <itemizedlist>
- <listitem>
+ <itemizedlist>
+ <!-- <listitem>
<para>
<filename>Hibernate Core</filename> Updated from 3.2.4.SP1_CP06 to 3.2.4.SP1.CP07
</para>
@@ -127,11 +127,26 @@
<filename>jboss-cache</filename>: Updated from 1.4.1.SP9 to 1.4.1.SP10
</para>
</listitem> -->
+ <listitem>
+ <para>
+ <filename>jboss-el</filename>: Updated to 1.0_02.CR3
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>jboss-embedded</filename>: Updated to beta3.SP5
+ </para>
+ </listitem>
<!-- <listitem>
<para>
<filename>jboss-system</filename>: Updated from 4.3.0.GA_CP02 to 4.3.0.GA_CP03
</para>
</listitem> -->
+ <listitem>
+ <para>
+ <filename>jboss-jpdl</filename>: Updated to 3.2.5.SP5
+ </para>
+ </listitem>
<!-- <listitem>
<para>
<filename>jboss-jmx</filename>: Updated from 4.3.0.GA_CP02 to 4.3.0.GA_CP03
@@ -167,7 +182,7 @@
<filename>jboss-embedded</filename>: Updated from beta3.SP2 to beta3.SP4
</para>
</listitem> -->
- <!-- </itemizedlist> -->
+ </itemizedlist>
</section>
</section>
<section id="Upgrading_or_Installating_a_Feature_Pack_for_the_first_time">
@@ -534,6 +549,86 @@
</para>
</important>
<itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1969">JBPAPP-1969</ulink>: The anchor in the pdf header and footer would fail and generate a <exceptionname>RuntimeException</exceptionname> detailing that not all of the annotations could be added to the document. This <emphasis>itext</emphasis> issue has been fixed by modifying the <classname>UIDocument</classname> classes <methodname>encodeEnd</methodname> method so that the document Header and Footer are reset so that information can be successfully added.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1928">JBPAPP-1928</ulink>: Within the <filename>Seambay</filename> example, if a user submitted an empty registration it would generate a debug page because of a <exceptionname>org.hibernate.validator.InvalidStateException</exceptionname>. This bug has been fixed by adding form validation to the example through the modification of the <filename>register.xhtml</filename> files form registration section.
+ </para>
+ </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.
+ </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.
+ </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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1916">JBPAPP-1916</ulink>: <classname>seam-gen</classname> did not handle the hibernate <property>@Type</property> of <varname>yes_no</varname> correctly and would have a <property>@Length</property> annotation for boolean types. These bugs have been corrected so that <classname>seam-gen</classname> correctly understands the Hibernate <property>@Type</property> of <varname>yes_no</varname> and the <property>@Length</property> annotation is not used for boolean types. In order for these changes to take place, the <filename>seam-gen/build.xml</filename> file has been updated with these changes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1915">JBPAPP-1915</ulink>: <classname>seam-gen</classname> would not ask for the jboss configuration name meaning that any deployment is always undertaken to the default configuration when <classname>seam-gen</classname> should be able to deploy to a different configuration. The main files to be updated for this fix are the <filename>build.properties</filename> and <filename>seam-gen/build.xml</filename> files that now allow for the jboss domain to be specified by a user so that any jboss configuration can be used.
+ </para>
+ </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.
+ </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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1911">JBPAPP-1911</ulink>: An unclosed input stream existed within the <methodname>writeResource</methodname> method of the <classname>Remoting</classname> class, causing a warning to be displayed to a user upon redeployment on GlassFish. The <classname>Remoting</classname> class has been modified with the inclusion of a try and catch block added to encompass the code and make sure the exception is not displayed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1910">JBPAPP-1910</ulink>: The DVD example that is distributed with the Seam component would generate a <exceptionname>JbpmException</exceptionname> when an order was canceled. The <filename>ordermanagement2.jpdl.xml</filename> and <filename>ordermanagement3.jpdl.xml</filename> files have each had the following line added: <code><transition name="cancel" to="cancelled"/></code>. The addition of this line to both files allows for the example to function correctly and not generate an exception.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1909">JBPAPP-1909</ulink>: Using Seam would grant a user a lower capacity to access methods in a reflected class than with Java directly. To allow Seam improved functionality in this area the <classname>RootInvocationContext</classname> class has been improved by including a call to <methodname>method.setAccessible(true)</methodname> within the <methodname>proceed</methodname> object.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1908">JBPAPP-1908</ulink>: The project build of a <classname>seam-gen</classname> project did not use the debug property except to load Groovy scripts dynamically. In this release the property also impacts:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Whether the <filename>jboss-seam-debug.jar</filename> is included in the archive
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Facelets development mode setting in <filename>web.xml</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The debug property used to replace the <property>@debug@</property> token within the <filename>components.xml</filename> file at runtime
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
<!-- <listitem>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>: Some components within the Feature Pack have been upgraded to the same version within the Enterprise Application Platform 4.3.0.CP05 release. A list of these components follows with further indepth information avaliable for each in the release notes for 4.3.0.CP05 avaliable at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.3.0.cp05/html-single/readme/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.3.0.cp05/html-single/readme/index.html</ulink>. The list of updated components are:
More information about the jboss-cvs-commits
mailing list