[jboss-cvs] JBossAS SVN: r82102 - projects/docs/enterprise/4.3.3.1/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Dec 7 22:25:49 EST 2008
Author: irooskov at redhat.com
Date: 2008-12-07 22:25:48 -0500 (Sun, 07 Dec 2008)
New Revision: 82102
Modified:
projects/docs/enterprise/4.3.3.1/readme/en-US/Release_Notes_CP03_FP01.xml
Log:
updated release notes with new JIRAs
Modified: projects/docs/enterprise/4.3.3.1/readme/en-US/Release_Notes_CP03_FP01.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/readme/en-US/Release_Notes_CP03_FP01.xml 2008-12-08 03:15:08 UTC (rev 82101)
+++ projects/docs/enterprise/4.3.3.1/readme/en-US/Release_Notes_CP03_FP01.xml 2008-12-08 03:25:48 UTC (rev 82102)
@@ -1,6 +1,6 @@
<?xml version="1.0"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
-<article id="JBEAP-Release-Notes">
+<article id="JBEAP-Release-Notes" status="draft">
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/>
<section id="Overview">
<title>Overview</title>
@@ -9,7 +9,7 @@
</para>
<para>
This feature pack provides a fully supported way to upgrade Seam currently included in EAP
- (Enterprise App Platform) 4.3 to the latest stable, production release (Seam 2.0.2.FP). It also
+ (Enterprise App Platform) 4.3 to Seam 2.0.2.FP. It also
includes a Technology Preview of Hibernate Search 3.0.
</para>
</section>
@@ -89,19 +89,33 @@
</note>
</section>
</section>
- <section id="Installation_Notes">
- <title>Installation Notes</title>
+<section id="Upgrading_or_Installating_a_Feature_Pack_for_the_first_time">
+ <title>Upgrading or Installing a Feature Pack for the first time</title>
<para>
- This section contains information related to installing JBoss Enterprise Application Platform Feature Pack version &VERSION;, including hardware and platform requirements and prerequisites.
+ The sections to follow detail how to upgrade from a previous Feature Pack release or install a Feature Pack for the first time.
</para>
+ <important>
+ <para>
+ If you have previously installed 4.3.0.CP02_FP01 then you will need to follow the details in the Upgrade section, otherwise follow the instructions within the Installation section.
+ </para>
+ </important>
+ <section id="upgrade">
+ <title>Upgrade Notes</title>
+ <para>
+ This section contains information related to upgrading from JBoss Enterprise Application Platform Feature Pack version 4.3.0_CP02_FP01, including hardware and platform requirements and prerequisites.
+ </para>
+ </section>
<section id="install">
<title>Installation Notes</title>
<para>
+ This section contains information related to installing JBoss Enterprise Application Platform Feature Pack version &VERSION; where a previous Feature Pack has not been installed before, including hardware and platform requirements and prerequisites.
+ </para>
+ <para>
To install this Feature Pack, unpack the contents of the archive into the root of your JBoss Enterprise Application Platform installation, which must be version 4.3.0_CP03.
</para>
<important>
<para>
- The contents of the Feature Pack should not be placed within a seperate folder in the EAP directory, but instead it should be intergrated with the current installation.
+ The contents of the Feature Pack should not be placed within a separate folder in the EAP directory, but instead it should be intergrated with the current installation.
</para>
</important>
<para>
@@ -361,24 +375,36 @@
</para>
</important>
<formalpara>
+ <title>JBPAPP-1466</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1466">JBPAPP-1466</ulink>: Numerous seam-gen updates have been applied from the latest version. Of special note, a recurring issue where a component would be joined with a property that was cast to a utility has been changed so that it is either uncapped or capped first.
+ </para>
+ </formalpara>
+ <formalpara>
<title>JBPAPP-1444</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1444">JBPAPP-1444</ulink>: AJAX request handling has been impoved in Seam. An error was present where when saving edits by clicking the <guibutton>Save</guibutton> button directly after editing a page in the <literal>Seam-gen</literal> gererated application, a <filename>Faces</filename> error message would display saying <errortext>The conversation ended, timed out or was processing another request</errortext>. In order to improve how Seam handles an AJAX request, a timeout feature has been implemented along with an AJAX error message given and the Seam Reference Guide Conversations chapter updated. For the user this means that if an AJAX request is sent to Seam in the circumstance noted, the request will be aborted and the appropriate AJAX error sent to the user.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1444">JBPAPP-1444</ulink>: AJAX request handling has been improved in Seam. An error was present where when saving edits by clicking the <guibutton>Save</guibutton> button directly after editing a page in the <literal>Seam-gen</literal> generated application, a <filename>Faces</filename> error message would display saying <errortext>The conversation ended, timed out or was processing another request</errortext>. In order to improve how Seam handles an AJAX request, a timeout feature has been implemented along with an AJAX error message given and the Seam Reference Guide Conversations chapter updated. For the user this means that if an AJAX request is sent to Seam in the circumstance noted, the request will be aborted and the appropriate AJAX error sent to the user.
</para>
</formalpara>
<formalpara>
<title>JBPAPP-1442</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1442">JBPAPP-1442</ulink>: A <exceptionname>NullPointerException</exceptionname> would occur when the <property>s:graphicalImage</property> property was given an Expression Language (EL) value that incorporated a null value. The <filename>GraphicImageResource.java</filename> file has been updated so that the occurances of where the property <property>image</property> is null and the property <property>image.getImage()</property> is null are tested before executing.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1442">JBPAPP-1442</ulink>: A <exceptionname>NullPointerException</exceptionname> would occur when the <property>s:graphicalImage</property> property was given an Expression Language (EL) value that incorporated a null value. The <filename>GraphicImageResource.java</filename> file has been updated so that the occurrences of where the property <property>image</property> is null and the property <property>image.getImage()</property> is null are tested before executing.
</para>
</formalpara>
<formalpara>
<title>JBPAPP-1411</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1411">JBPAPP-1411</ulink>: The conversation switcher housed within <filename>Switcher.java</filename> did not work correctly with natural conversations, interpreting them as views. In order to ammend this, the method <methodname>select()</methodname> within <filename>Switcher.java</filename> has been modified so that the value of <property>isOutcome</property> correctly includes the index of the <property>conversationIdOrOutcome</property>. With this corrected, the conversation switcher now works correctly.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1411">JBPAPP-1411</ulink>: The conversation switcher housed within <filename>Switcher.java</filename> did not work correctly with natural conversations, interpreting them as views. In order to amend this, the method <methodname>select()</methodname> within <filename>Switcher.java</filename> has been modified so that the value of <property>isOutcome</property> correctly includes the index of the <property>conversationIdOrOutcome</property>. With this corrected, the conversation switcher now works correctly.
</para>
</formalpara>
<formalpara>
+ <title>JBPAPP-1361</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1361">JBPAPP-1361</ulink>: When using a custom back-end to Hibernate and then using a delete call in relation to an annotated Person entity, a <exceptionname>DeleteLuceneWork</exceptionname> exception as well as a <exceptionname>AddLuceneWork</exceptionname> exception would occur when only the former should have. To correct this issue by Hibernate Core, when the Core does an update and then a delete on the same entity, the delete call is ignored.
+ </para>
+ </formalpara>
+ <formalpara>
<title>JBPAPP-1327</title>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1327">JBPAPP-1327</ulink>: While running the chatroom example a message could be sent and display the user as <emphasis>null></emphasis> even if a connection did not exist. This update to the CP makes sure that this eventuality does not occur by continually make sure the <code>connectedFlag</code> within <filename>chatroom.js</filename> is set correctly within the relevant methods and that this is tested for.
@@ -405,7 +431,7 @@
<formalpara>
<title>JBPAPP-1323</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1323">JBPAPP-1323</ulink>: The urlBase attribute on <code><m:message></code> would never have been used becasue of the way in which the code was written. The method <methodname>encodeBegin</methodname> within <filename>UIMessage.java</filename> has been re-written so that urlBase is able to be used.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1323">JBPAPP-1323</ulink>: The urlBase attribute on <code><m:message></code> would never have been used because of the way in which the code was written. The method <methodname>encodeBegin</methodname> within <filename>UIMessage.java</filename> has been re-written so that urlBase is able to be used.
</para>
</formalpara>
<formalpara>
@@ -429,7 +455,7 @@
<formalpara>
<title>JBPAPP-1319</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1319">JBPAPP-1319</ulink>: A <exceptionname>NotEntityException</exceptionname> would occur on occassion when utilizing the <classname>HibernatePersistanceProvider</classname>. In order to rectify this, the <exceptionname>TransientObjectException</exceptionname> is cought.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1319">JBPAPP-1319</ulink>: A <exceptionname>NotEntityException</exceptionname> would occur on occasion when utilizing the <classname>HibernatePersistanceProvider</classname>. In order to rectify this, the <exceptionname>TransientObjectException</exceptionname> is caught.
</para>
</formalpara>
<formalpara>
@@ -447,7 +473,7 @@
<formalpara>
<title>JBPAPP-1315</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1315">JBPAPP-1315</ulink>: The Seam debug page would not be displyed properly within <filename>.page.xml</filename> pages. To inable the proper exceptions to be read, the <filename>debug.xhtml</filename> file has been modified so that <code>Caused by #{exception.class.name} with message: "#{exception.message}"</code> has been changed to <code>Caused by #{exception.class.name} with message: "#{exception.getMessage()}"</code>, enabling the corect exceptions to be readable.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1315">JBPAPP-1315</ulink>: The Seam debug page would not be displayed properly within <filename>.page.xml</filename> pages. To inable the proper exceptions to be read, the <filename>debug.xhtml</filename> file has been modified so that <code>Caused by #{exception.class.name} with message: "#{exception.message}"</code> has been changed to <code>Caused by #{exception.class.name} with message: "#{exception.getMessage()}"</code>, enabling the correct exceptions to be readable.
</para>
</formalpara>
<formalpara>
@@ -471,7 +497,7 @@
<formalpara>
<title>JBPAPP-1309</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1309">JBPAPP-1309</ulink>: A paragraph has been added to the Configuration seciton of the Seam Reference Guide which explains that for a browser <guibutton>Back</guibutton> button to work correctly, the following context parameter needs to be included:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1309">JBPAPP-1309</ulink>: A paragraph has been added to the Configuration section of the Seam Reference Guide which explains that for a browser <guibutton>Back</guibutton> button to work correctly, the following context parameter needs to be included:
</para>
</formalpara>
<programlisting>
@@ -501,13 +527,13 @@
<formalpara>
<title>JBPAPP-1300</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1300">JBPAPP-1300</ulink>: If Seam ever encountered a closed Entity Manager or Hibernate Session then it would attempt to change the flush mode and produce an error as a response. In order for Seam not to attempt a change of the flush mode f the Entity Manager or Hibernate Sessions is closed, a check of if the Entity Manager is open has been added to <filename>ManagedPersistenceContext.java</filename> and a check of if a Hibernate Session is open has been added to <filename>ManagedHibernateSessions.java</filename>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1300">JBPAPP-1300</ulink>: If Seam ever encountered a closed Entity Manager or Hibernate Session then it would attempt to change the flush mode and produce an error as a response. In order for Seam not to attempt a change of the flush mode if the Entity Manager or Hibernate Sessions is closed, a check of if the Entity Manager is open has been added to <filename>ManagedPersistenceContext.java</filename> and a check of if a Hibernate Session is open has been added to <filename>ManagedHibernateSessions.java</filename>.
</para>
</formalpara>
<formalpara>
<title>JBPAPP-1299</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1299">JBPAPP-1299</ulink>: An error existed in the examples of Seam where if the <guibutton>back</guibutton> button was used to navigate back to the main page then a <exceptionname>ViewExpiredException</exceptionname> would occur. To avoid this, the exception is now cought and the user is redirected to the home page with a <errortype>Session Expired</errortype> message is displayed. The affected examples were <filename>Spring</filename>, <filename>JPA</filename>, <filename>Nestedbooking</filename>, <filename>Hibernate</filename>, <filename>Icefaces</filename> and <filename>Groovybooking</filename> and the code added to these examples to implement the change is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1299">JBPAPP-1299</ulink>: An error existed in the examples of Seam where if the <guibutton>back</guibutton> button was used to navigate back to the main page then a <exceptionname>ViewExpiredException</exceptionname> would occur. To avoid this, the exception is now caught and the user is redirected to the home page with a <errortype>Session Expired</errortype> message is displayed. The affected examples were <filename>Spring</filename>, <filename>JPA</filename>, <filename>Nestedbooking</filename>, <filename>Hibernate</filename>, <filename>Icefaces</filename> and <filename>Groovybooking</filename> and the code added to these examples to implement the change is as follows:
</para>
</formalpara>
<programlisting>
@@ -546,19 +572,19 @@
<formalpara>
<title>JBPAPP-1296</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1296">JBPAPP-1296</ulink>: The <filename>Filter.java</filename> file was not serializable, leading to a <exceptionname>NotSerializableException</exceptionname>. This FP release corrects this issue by editing the <filename>Filter.java</filename> file so that it impements the serializable paramters.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1296">JBPAPP-1296</ulink>: The <filename>Filter.java</filename> file was not serializable, leading to a <exceptionname>NotSerializableException</exceptionname>. This FP release corrects this issue by editing the <filename>Filter.java</filename> file so that it implements the serializable parameters.
</para>
</formalpara>
<formalpara>
<title>JBPAPP-1295</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1295">JBPAPP-1295</ulink>: The password page was accessable to users that were not logged in. To change this the navigation rule for <filename>passowrd.xhtml</filename> was rewritten within <filename>pages.xml</filename> so that if a user who is not logged in attempts to access the password page they will be redirected to the home page.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1295">JBPAPP-1295</ulink>: The password page was accessable to users that were not logged in. To change this the navigation rule for <filename>password.xhtml</filename> was rewritten within <filename>pages.xml</filename> so that if a user who is not logged in attempts to access the password page they will be redirected to the home page.
</para>
</formalpara>
<formalpara>
<title>JBPAPP-1294</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1294">JBPAPP-1294</ulink>: An error was apparent within the <filename>QuartzDispatcher.java</filename> file which would cause a new <emphasis>SimpleTigger</emphasis> to be created with a null <property>startTime</property>, which is a forbidden value for the attribute. This issue has been fixed by modifying the <emphasis>SimpleTrigger</emphasis> creation line within <filename>QuartzDispatcher.java</filename> so that the <property>startTime</property> attribute is now set to <code>new Date()</code>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1294">JBPAPP-1294</ulink>: An error was apparent within the <filename>QuartzDispatcher.java</filename> file which would cause a new <emphasis>SimpleTrigger</emphasis> to be created with a null <property>startTime</property>, which is a forbidden value for the attribute. This issue has been fixed by modifying the <emphasis>SimpleTrigger</emphasis> creation line within <filename>QuartzDispatcher.java</filename> so that the <property>startTime</property> attribute is now set to <code>new Date()</code>.
</para>
</formalpara>
<!-- <formalpara>
@@ -570,13 +596,13 @@
<formalpara>
<title>JBPAPP-1192</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1192">JBPAPP-1192</ulink>: A business process variable <varname>bannersCount</varname> was not resolveable in jPDL (Java Process Definition Language). Om prder to correct this bug, code within <filename>SeamExpressionEvaluator.java</filename> has been reordered and a new test process has been added to <filename>SeamExpressionEvaluatorTest.java</filename> and <filename>SeamExpressionEvaluatorTestController.java</filename> for debugging.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1192">JBPAPP-1192</ulink>: A business process variable <varname>bannersCount</varname> was not resolveable in jPDL (Java Process Definition Language). In order to correct this bug, code within <filename>SeamExpressionEvaluator.java</filename> has been reordered and a new test process has been added to <filename>SeamExpressionEvaluatorTest.java</filename> and <filename>SeamExpressionEvaluatorTestController.java</filename> for debugging.
</para>
</formalpara>
<formalpara>
<title>JBPAPP-1156</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1156">JBPAPP-1156</ulink>: <filename>seam-gen</filename> generated tests would fail to work when run using JDK6. This descrepancy has been correct by modifying the <filename>build.xml</filename> and <filename>build-war.xml</filename> files of the <filename>seam-gen</filename> build scripts with the following addition:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1156">JBPAPP-1156</ulink>: <filename>seam-gen</filename> generated tests would fail to work when run using JDK6. This discrepancy has been correct by modifying the <filename>build.xml</filename> and <filename>build-war.xml</filename> files of the <filename>seam-gen</filename> build scripts with the following addition:
</para>
</formalpara>
<programlisting>
More information about the jboss-cvs-commits
mailing list