[jboss-cvs] JBossAS SVN: r79250 - in projects/docs/enterprise: 4.3.3/Getting_Started/en-US and 1 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Oct 7 23:43:10 EDT 2008
Author: irooskov at redhat.com
Date: 2008-10-07 23:43:09 -0400 (Tue, 07 Oct 2008)
New Revision: 79250
Modified:
projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml
projects/docs/enterprise/4.3.3/Getting_Started/en-US/Directory_Structure.xml
projects/docs/enterprise/4.3.3/Getting_Started/en-US/Getting_Started_Guide_CP03.xml
projects/docs/enterprise/4.3.3/Getting_Started/en-US/Server_Configurations.xml
projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml
Log:
updated release notes with new JIRAs and began work to try and have the Getting Started guide building as a pdf
Modified: projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml
===================================================================
--- projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml 2008-10-08 02:13:13 UTC (rev 79249)
+++ projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml 2008-10-08 03:43:09 UTC (rev 79250)
@@ -275,6 +275,16 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1253">JBPAPP-1253</ulink>: Implementations of the <classname>ValidConnectionChecker</classname> class were not serializable. The way in which the implementations handle excepetion cases has been rewritten, along with the testing of valid connections. By recoding these methods, the implementations are now serializable.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1252">JBPAPP-1252</ulink>: Both methods <methodname>afterCompletion</methodname> and the called method <methodname>unregisterConnection</methodname> within <filename>TxConnectionManager.java</filename> would return a connection to the pool and the <classname>InternalManagedConnectionPool</classname> class was not able to handle duplicates causing problems such as a leaked connection permit with an eventual overflow of the pool. The way in which the connections are managed has been modified to correct a race condition between the methods <methodname>connection.close()</methodname> and <methodname>transaction.rollback()</methodname> that in turn ensures no duplication of connections in the pool.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1227">JBPAPP-1227</ulink>: There was an issue where the timerServiceMap within the EJBTimerServiceImpl implementation should be synchornized. In order to allow for this the following methods have been modified:
<itemizedlist>
<listitem>
@@ -307,6 +317,24 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1212">JBPAPP-1212</ulink>: JBoss Remoting has been upgraded to version 2.2.2.SP10, fixing five major bugs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1208">JBPAPP-1208</ulink>: When load time weaving was enabled a <exceptionname>ConcurrentModificationException</exceptionname> would appear in the jboss log output for <methodname>JoinpointSimpleClassifier.classifyJoinpoint</methodname>. This bug in reporting has been rectified with these updated packages.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1207">JBPAPP-1207</ulink>: A bug existed where when tx would commit and cache would wish to remove a directory from its structure as in removing /a/b and adding /a/b/d through cache, then the remove would not be successful. This failure was a result of the program failing to traverse the children of a given directory and instead seeing that both had /a/b/ and thus the add had made the remove obsolete.
+ </para>
+ <para>
+ In correcting this issue the <filename>TreeCache.java</filename> file has been altered to include the successful mapping of a directories children by use of an interator and the <filename>RemoveOnTxTest.java</filename> file was altered to check if children are marked for deletion.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1205">JBPAPP-1205</ulink>: When using an Oracle Driver without an offset, the query that is generated ommits <code>rownum > 0</code>. This resulted in an incorrect number of rows being returned. This issue is fixed with this CP release and the aforementioned code is now included.
</para>
</listitem>
@@ -322,6 +350,16 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1199">JBPAPP-1199</ulink>: The system properties within <filename>jboss-aop.xml</filename> has been upgraded to incorporate the ability to use environment variables.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1198">JBPAPP-1198</ulink>: Marshalling logic within <classname>TreeCacheMarshaller140</classname> used to use a HashMap to store objects that were previously written in order to easily refer to this through a number for subsequent writes. Use of the HashMap however allowed for an object that only satisfied the method <methodname>equals()</methodname> but did not adhrere to an <code>==</code> assignment, to be incorrectly detected as being of the same identity. Correcting this issue has seen the HashMap programming change to the use of a <classname>java.util.IdentityHashMap</classname> instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1195">JBPAPP-1195</ulink>: The <classname>UsernameToken</classname> implementation was mandating that the <property>wsu:id</property> attribute be included on incomming requests. The way in which the <filename>Timestamp.java</filename>, <filename>UsernameToken.java</filename> and <filename>X509Token.java</filename> files opperate has been updated in order to correct this issue.
</para>
</listitem>
@@ -332,6 +370,21 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1179">JBPAPP-1179</ulink>: The Apache JServ Protocol (AJP) connector handle posted data as a request header if an exception or error occured before reading the data and the data was between 512 and 767.This issue has been fixed for this latest CP release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1165">JBPAPP-1165</ulink>: There was a request to add a <property>socketBuffer</property> attribute to the HTTP connector in order to allow the specification of a custom buffer size. This addition has been incorporated with the possibility of TCP traffic reduction while improving performance of large responses when suffiecient memory is avaliable to support buffer size increases.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1140">JBPAPP-1140</ulink>: JBoss AOP has been upgraded to version 1.5.5.CP03.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1111">JBPAPP-1111</ulink>: The section on max-bean-life within the Server Configuration Guide required improvement so that no abiguity would exist in the Japanese translation. This issue has been fixed by rewording the English sentence that caused the issue.
</para>
</listitem>
@@ -374,6 +427,11 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1049">JBPAPP-1049</ulink>: JBoss Web has been upgraded to version 2.0.0.CP08 for this latest JBoss Enterprise Application Platform CP release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1046">JBPAPP-1046</ulink>: There was an error in the Spring example where if a user created an invalid booking, the example would still allow the booking to proceed. The booking would not be stored and an <exceptionname>IllegalStateException</exceptionname> would be generated when the user tried to start a new conversation. To rectify this issue, a rule element has been added into the <filename>pages.xml</filename> file to insure the validity of the booking.
</para>
</listitem>
Modified: projects/docs/enterprise/4.3.3/Getting_Started/en-US/Directory_Structure.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Getting_Started/en-US/Directory_Structure.xml 2008-10-08 02:13:13 UTC (rev 79249)
+++ projects/docs/enterprise/4.3.3/Getting_Started/en-US/Directory_Structure.xml 2008-10-08 03:43:09 UTC (rev 79250)
@@ -79,12 +79,11 @@
<para>
The table below illustrates the contents of the <filename class="directory">jboss-as</filename> directory.
</para>
- <para>
<table id="JBOSS_DISTjboss_as_Directory_Structure-Contents_of_JBOSS_DISTjboss_as_directory">
<title>Contents of <filename class="directory">JBOSS_DIST/jboss-as</filename> directory</title>
<tgroup cols="2">
- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
- <colspec colname="c2" colnum="2" colwidth="4*"></colspec>
+ <!-- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
+ <colspec colname="c2" colnum="2" colwidth="4*"></colspec> -->
<thead>
<row>
<entry>
@@ -139,6 +138,5 @@
</tbody>
</tgroup>
</table>
- </para>
</section>
</section>
\ No newline at end of file
Modified: projects/docs/enterprise/4.3.3/Getting_Started/en-US/Getting_Started_Guide_CP03.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Getting_Started/en-US/Getting_Started_Guide_CP03.xml 2008-10-08 02:13:13 UTC (rev 79249)
+++ projects/docs/enterprise/4.3.3/Getting_Started/en-US/Getting_Started_Guide_CP03.xml 2008-10-08 03:43:09 UTC (rev 79250)
@@ -3,15 +3,15 @@
]>
<book>
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Preface_1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="The_JBoss_Server___A_Quick_Tour.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="EJB3_Caveats.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="About_the_Example_Applications.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Sample_JSF_EJB3_Application.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Using_Seam.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Using_Other_Databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Preface_1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="The_JBoss_Server___A_Quick_Tour.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="EJB3_Caveats.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="About_the_Example_Applications.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Sample_JSF_EJB3_Application.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Using_Seam.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Using_Other_Databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<appendix id="Further_Information_Sources">
<title>Further Information Sources</title>
<para>
@@ -29,8 +29,8 @@
<para>
For complete coverage of the JBoss Seam framework, we recommend <emphasis>JBoss Seam: Simplicity And Power Beyond Java EE</emphasis>. (Prentice Hall, 2007. Michael Yuan, Thomas Heute).
</para>
- </appendix>
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
+ </appendix>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
</book>
Modified: projects/docs/enterprise/4.3.3/Getting_Started/en-US/Server_Configurations.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Getting_Started/en-US/Server_Configurations.xml 2008-10-08 02:13:13 UTC (rev 79249)
+++ projects/docs/enterprise/4.3.3/Getting_Started/en-US/Server_Configurations.xml 2008-10-08 03:43:09 UTC (rev 79250)
@@ -76,12 +76,11 @@
<para>
The directory server configuration you’re using, is effectively the server root while JBoss is running. It contains all the code and configuration information for the services provided by the particular server configuration. It’s where the log output goes, and it’s where you deploy your applications. <xref linkend="Server_Configuration_Directory_Structure-Server_Configuration_Directory_Structure" /> shows the directories inside the server configuration directory (<filename class="directory">JBOSS_DIST/jboss-as/server/<instance-name></filename>) and their functions.
</para>
- <para>
<table id="Server_Configuration_Directory_Structure-Server_Configuration_Directory_Structure">
<title>Server Configuration Directory Structure</title>
<tgroup cols="2">
- <colspec colname="c1" colnum="1" colwidth="1*"></colspec>
- <colspec colname="c2" colnum="2" colwidth="4*"></colspec>
+ <!--<colspec colname="c1" colnum="1" colwidth="1*"></colspec>
+ <colspec colname="c2" colnum="2" colwidth="4*"></colspec> -->
<thead>
<row>
<entry>
@@ -152,7 +151,6 @@
</tbody>
</tgroup>
</table>
- </para>
</section>
<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations-The_default_Server_Configuration_File_Set">
<title>The "default" Server Configuration File Set</title>
@@ -226,12 +224,11 @@
<para>
The files in the <literal>conf</literal> directory are explained in the following table.
</para>
- <para>
<table id="Contents_of_conf_directory-Contents_of_conf_directory">
<title>Contents of "conf" directory</title>
<tgroup cols="2">
- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
- <colspec colname="c2" colnum="2" colwidth="4*"></colspec>
+ <!-- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
+ <colspec colname="c2" colnum="2" colwidth="4*"></colspec> -->
<thead>
<row>
<entry>
@@ -326,7 +323,6 @@
</tbody>
</tgroup>
</table>
- </para>
</section>
<section id="The_default_Server_Configuration_File_Set-Contents_of_deploy_directory">
@@ -334,12 +330,11 @@
<para>
The files in the <literal>deploy</literal> directory are explained in the following table.
</para>
- <para>
<table id="Contents_of_deploy_directory-Contents_of_deploy_directory">
<title>Contents of "deploy" directory</title>
<tgroup cols="2">
- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
- <colspec colname="c2" colnum="2" colwidth="4*"></colspec>
+ <!-- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
+ <colspec colname="c2" colnum="2" colwidth="4*"></colspec> -->
<thead>
<row>
<entry>
@@ -642,7 +637,6 @@
</tbody>
</tgroup>
</table>
- </para>
</section>
</section>
@@ -651,12 +645,11 @@
<para>
The "all" server configuration file set is located in the <filename class="directory">JBOSS_DIST/jboss-as/server/all</filename> directory. In addition to the services in the "default" set, the all configuration contains several other services in the <literal>conf/</literal> directory as shown below.
</para>
- <para>
<table id="The_all_Server_Configuration_File_Set-Additional_Services_in_conf_directory_for_all_configuration">
<title>Additional Services in "conf" directory for "all" configuration</title>
<tgroup cols="2">
- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
- <colspec colname="c2" colnum="2" colwidth="4*"></colspec>
+ <!-- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
+ <colspec colname="c2" colnum="2" colwidth="4*"></colspec> -->
<thead>
<row>
<entry>
@@ -735,19 +728,17 @@
</tbody>
</tgroup>
</table>
- </para>
</section>
<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations-EJB3_Services_">
<title>EJB3 Services </title>
<para>
The following table explains the files providing ejb3 services.
</para>
- <para>
<table id="EJB3_Services_-EJB3_Services">
<title>EJB3 Services</title>
<tgroup cols="2">
- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
- <colspec colname="c2" colnum="2" colwidth="4*"></colspec>
+ <!-- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
+ <colspec colname="c2" colnum="2" colwidth="4*"></colspec> -->
<thead>
<row>
<entry>
@@ -794,16 +785,14 @@
</tbody>
</tgroup>
</table>
- </para>
<para>
Finally, in the EJB3 "all" configuration there are two additional services.
</para>
- <para>
<table id="EJB3_Services_-Additional_Services_in_EJB3_all_Configuration">
<title>Additional Services in EJB3 "all" Configuration</title>
<tgroup cols="2">
- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
- <colspec colname="c2" colnum="2" colwidth="4*"></colspec>
+ <!-- <colspec colname="c1" colnum="1" colwidth="4*"></colspec>
+ <colspec colname="c2" colnum="2" colwidth="4*"></colspec> -->
<thead>
<row>
<entry>
@@ -834,7 +823,6 @@
</tbody>
</tgroup>
</table>
- </para>
</section>
<section id="The_JBoss_Server___A_Quick_Tour-Server_Configurations-Adding_Your_Own_Configuration">
<title>Adding Your Own Configuration</title>
Modified: projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml
===================================================================
--- projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml 2008-10-08 02:13:13 UTC (rev 79249)
+++ projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml 2008-10-08 03:43:09 UTC (rev 79250)
@@ -277,28 +277,61 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1219">JBPAPP-1219</ulink>:JBoss Messaging would stop processing a message because the <classname>ConnectionValidator</classname> ping on the client side had timed out causing the <classname>LeasePinger</classname> to shut down and the server side <classname>Lease</classname> to report a connection failure. Once a connection failure had been reported to the registered listeners the <classname>ServerInvokerCallbackHandler</classname> would close its client and in turn change push callbacks into pull callbacks. To rectify this issue the following attributes have been added to the <filename>remoting-bisocket-service-xml</filename> file:
+ </para>
+<programlisting>
+<attribute name="validatorPingPeriod" isParam="true">10000</attribute>
+<attribute name="validatorPingTimeout" isParam="true">5000</attribute>
+<attribute name="registerCallbackListener">false</attribute>
+</programlisting>
+ <para>
+ The addition of these attributes insures that the <classname>Connectionvalidator</classname> ping does not time out so quickly, ensuring correct communications can occur.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1213">JBPAPP-1213</ulink>: JBoss Messaging has been upgraded to 1.4.0.SP3_CP04. This update corrects various bugs that existed in the earlier build of the component.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1067">JBPAPP-1067</ulink>: Configuration of the Messaging Queue value <property>DEFAULT_RECOVER_DELIVERIES_TIMEOUT </property> was set to 5 * 60 * 10000, when the final number in the sequence should be 1000. This bug fix has been included with these updated packages.
</para>
</listitem>
</itemizedlist>
</para>
</formalpara>
- <!-- <formalpara>
+ <formalpara>
<title>JBoss Cache</title>
<para>
<itemizedlist>
<listitem>
-
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1207">JBPAPP-1207</ulink>: A bug existed where when tx would commit and cache would wish to remove a directory from its structure as in removing /a/b and adding /a/b/d through cache, then the remove would not be successful. This failure was a result of the program failing to traverse the children of a given directory and instead seeing that both had /a/b/ and thus the add had made the remove obsolete.
+ </para>
+ <para>
+ In correcting this issue the <filename>TreeCache.java</filename> file has been altered to include the successful mapping of a directories children by use of an interator and the <filename>RemoveOnTxTest.java</filename> file was altered to check if children are marked for deletion.
+ </para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1198">JBPAPP-1198</ulink>: Marshalling logic within <classname>TreeCacheMarshaller140</classname> used to use a HashMap to store objects that were previously written in order to easily refer to this through a number for subsequent writes. Use of the HashMap however allowed for an object that only satisfied the method <methodname>equals()</methodname> but did not adhrere to an <code>==</code> assignment, to be incorrectly detected as being of the same identity. Correcting this issue has seen the HashMap programming change to the use of a <classname>java.util.IdentityHashMap</classname> instead.
+ </para>
+ </listitem>
</itemizedlist>
</para>
- </formalpara> -->
+ </formalpara>
<formalpara>
<title>JBoss Remoting</title>
<para>
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1212">JBPAPP-1212</ulink>: JBoss Remoting has been upgraded to version 2.2.2.SP10, fixing five major bugs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-934">JBPAPP-934</ulink>: Message Transmission Optimization Mechanism (MTOM) support was broken in earlier releases of the EAP. The bug has now been fixed and MTOM support is opperational.
</para>
</listitem>
@@ -311,6 +344,21 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1179">JBPAPP-1179</ulink>: The Apache JServ Protocol (AJP) connector handle posted data as a request header if an exception or error occured before reading the data and the data was between 512 and 767.This issue has been fixed for this latest CP release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1165">JBPAPP-1165</ulink>: There was a request to add a <property>socketBuffer</property> attribute to the HTTP connector in order to allow the specification of a custom buffer size. This addition has been incorporated with the possibility of TCP traffic reduction while improving performance of large responses when suffiecient memory is avaliable to support buffer size increases.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1049">JBPAPP-1049</ulink>: JBoss Web has been upgraded to version 2.0.0.CP08 for this latest JBoss Enterprise Application Platform CP release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-882">JBPAPP-882</ulink>: The Java Server Faces (JSF) needed its libraries to be upgraded to 1.2_09-b01. This issue has been fixed by upgrading to version 1.2_09 of the libraries, which is no longer in beta.
</para>
</listitem>
@@ -345,6 +393,11 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1129">JBPAPP-1129</ulink>: An issue was apparent where the icefaces example would not work given the setup of certain EAP environments. In order to fix this bug, the jsf libraries have been upgraded for this example.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1093">JBPAPP-1093</ulink>: The numberguess example asked that the user guess a number between 1 and 100 enclusive, however the application would generate a number between 0 and 99 inclusive. The issue has now been rectified so that the number a user can guess and the numbers the example can generate are the same.
</para>
</listitem>
@@ -515,6 +568,18 @@
</para>
</formalpara>
<formalpara>
+ <title>JBPAPP-1253</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1253">JBPAPP-1253</ulink>: Implementations of the <classname>ValidConnectionChecker</classname> class were not serializable. The way in which the implementations handle excepetion cases has been rewritten, along with the testing of valid connections. By recoding these methods, the implementations are now serializable.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-1252</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1252">JBPAPP-1252</ulink>: Both methods <methodname>afterCompletion</methodname> and the called method <methodname>unregisterConnection</methodname> within <filename>TxConnectionManager.java</filename> would return a connection to the pool and the <classname>InternalManagedConnectionPool</classname> class was not able to handle duplicates causing problems such as a leaked connection permit with an eventual overflow of the pool. The way in which the connections are managed has been modified to correct a race condition between the methods <methodname>connection.close()</methodname> and <methodname>transaction.rollback()</methodname> that in turn ensures no duplication of connections in the pool.
+ </para>
+ </formalpara>
+ <formalpara>
<title>JBPAPP-1227</title>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1227">JBPAPP-1227</ulink>: There was an issue where the timerServiceMap within the EJBTimerServiceImpl implementation should be synchornized. In order to allow for this the following methods have been modified:
@@ -543,12 +608,30 @@
</para>
</formalpara>
<formalpara>
+ <title>JBPAPP-1208</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1208">JBPAPP-1208</ulink>: When load time weaving was enabled a <exceptionname>ConcurrentModificationException</exceptionname> would appear in the jboss log output for <methodname>JoinpointSimpleClassifier.classifyJoinpoint</methodname>. This bug in reporting has been rectified with these updated packages.
+ </para>
+ </formalpara>
+ <formalpara>
<title>JBPAPP-1201</title>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1201">JBPAPP-1201</ulink>: When removing a Stateful Session Bean, references would still remain in the infinite pool causing a memory leak. The removal of a Stateful Session Bean is now undertaken correctly so that all references are removed from the infinite pool when the bean is destroyed.
</para>
</formalpara>
<formalpara>
+ <title>JBPAPP-1199</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1199">JBPAPP-1199</ulink>: The system properties within <filename>jboss-aop.xml</filename> has been upgraded to incorporate the ability to use environment variables.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-1140</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1140">JBPAPP-1140</ulink>: JBoss AOP has been upgraded to version 1.5.5.CP03.
+ </para>
+ </formalpara>
+ <formalpara>
<title>JBPAPP-933</title>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-933">JBPAPP-933</ulink>: When deploying an Enterprise JavaBeans 2 (EJB2) after starting a Service Bean with a Naming context associated with the applications class loader, the EJB2 will fail as it binds with the applications UnifiedClassLoader instead.
More information about the jboss-cvs-commits
mailing list