[jboss-cvs] JBossAS SVN: r79051 - in projects/docs/enterprise: 4.2.5/readme/en-US and 2 other directories.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Thu Oct 2 22:00:47 EDT 2008


Author: irooskov at redhat.com
Date: 2008-10-02 22:00:47 -0400 (Thu, 02 Oct 2008)
New Revision: 79051

Modified:
   projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Getting_Started.xml
   projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml
   projects/docs/enterprise/4.3.3/Installation_Guide/en-US/Getting_Started.xml
   projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml
Log:
release notes updated with new jira


Modified: projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Getting_Started.xml	2008-10-03 00:36:49 UTC (rev 79050)
+++ projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Getting_Started.xml	2008-10-03 02:00:47 UTC (rev 79051)
@@ -240,7 +240,7 @@
 		<section id="Pre_Requisites-Configuring_Your_Java_Environment">
 			<title>Configuring Your Java Environment</title>
 			<para>
-				You must have a working installation of <emphasis role="bold">JDK 1.5</emphasis> before you install &JBEAP;. You can install the 32-bit or 64-bit JVM as per your requirements. In this guide we will show you how to install a 32-bit Sun JDK 5.0 on a Linux Platform and Microsoft Windows Platform. But before we do that let's take a look at some of the benefits of using a 64-bit JVM.
+				You must have a working installation of <emphasis role="bold">JDK 1.5</emphasis> before you install &JBEAP;. You can install the 32-bit or 64-bit JVM as per your requirements. In this guide we will show you how to install a 32-bit Sun JDK 5.0 using RHN, on a generic Linux Platform and Microsoft Windows Platform But before we do that let's take a look at some of the benefits of using a 64-bit JVM.
 				<itemizedlist id="Configuring_Your_Java_Environment-Benefits_of_64_bit_JVM_on_64_bit_OS_and_Hardware">
 					<title>Benefits of 64-bit JVM on 64-bit OS and Hardware:</title>
 					<listitem>
@@ -264,10 +264,59 @@
 						</para>
 					</listitem>
 				</itemizedlist>
-				<itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_on_Linux">
-					<title>Installing and Configuring 32-bit Sun JDK 5.0 on Linux</title>
+				<itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_using_RHN">
+					<title>Installing and Configuring 32-bit Sun JDK 5.0 using RHN</title>
 					<listitem>
 						<para>
+							Java SDKs are provided by the Red Hat Enterprise Linux 5  Supplementary channel for your Linux variant and architecture. Depending on the architecture, the channel names are:
+						</para>
+						<para>
+							rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementary-5
+						</para>
+						<para>
+							The <command moreinfo="none">java-1.5.0-bea</command>,
+							<command moreinfo="none">java-1.5.0-ibm</command> and
+							<command moreinfo="none">java-1.5.0-sun</command> SDKs are available from
+							these channels. Make sure you also install the
+							<command moreinfo="none">-devel</command> subpackages.
+						</para>
+					</listitem>
+					
+					<listitem>
+						<para>
+							Selecting <command moreinfo="none">alternatives</command> for <command moreinfo="none">java</command>, <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.5.0</command> (setting <command moreinfo="none">java_sdk_1.5.0</command> is optional). 
+						</para>
+						
+						<para>
+							This is only needed if you want to use the SysV service script
+							and/or want this installed SDK to be the default java and javac
+							in the system. This choice can often be overridden by setting
+							the <command moreinfo="none">JAVA_HOME</command> environment variable.
+						</para>
+						
+						<para>
+							The <command moreinfo="none">alternatives</command> system allows different versions of Java, from different sources to co-exist on your system. You should make sure the desired one is selected so that the service script uses the one you want.
+						</para>
+						
+						<para>
+							As root, issue the following command:
+						</para>
+						<screen>
+							<command moreinfo="none">/usr/sbin/alternatives --config java</command>
+						</screen>
+						<para>
+							and make sure the desired one is selected (marked with a '+'), or select it by entering its number as prompted.
+						</para>
+						
+						<para>
+							Make sure you do the same for <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.5.0.</command> We recommend that all point to the same manufacturer and version.
+						</para>
+					</listitem>
+				</itemizedlist>
+				<itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_on_a_generic_Linux_platform">
+					<title>Installing and Configuring 32-bit Sun JDK 5.0 on a generic Linux platform</title>
+					<listitem>
+						<para>
 							Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun&#39;s website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp"></ulink>. Choose "JDK 5.0 Update &lt;x&gt;" (where x is the latest update number) for download and then select "RPM in self-extracting" file for Linux<footnote><para>Make sure you choose the appropriate file for your platform.</para></footnote>. Read the instructions on Sun&#39;s website for installing the JDK.
 						</para>
 					</listitem>

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-03 00:36:49 UTC (rev 79050)
+++ projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml	2008-10-03 02:00:47 UTC (rev 79051)
@@ -275,6 +275,38 @@
 		<itemizedlist>
 			<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>
+							<para>
+								removeTimerService (variation 2)
+							</para>
+						</listitem>
+						<listitem>
+							<para>
+								removeTimerService (variation 3)
+							</para>
+						</listitem>
+						<listitem>
+							<para>
+								String listTimers
+							</para>
+						</listitem>
+					</itemizedlist>
+					<note>
+						<para>
+							Variation numbering is based upon when each method appears in the code.
+						</para>
+					</note>
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1217">JBPAPP-1217</ulink>: The Installation Guide did not provide correct information on how a Red Hat Enterprise Linux customer would install or update their Java JDK using Red Hat Network (RHN). This necessary information has now been included and the distinction made between the Red Hat Enterprise Linux customer Java installation method and installing Java on a generic Linux distribution. 
+				</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>
@@ -290,6 +322,11 @@
 			</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>
+			<listitem>
+				<para>
 					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1185">JBPAPP-1185</ulink>:  A test case <methodname>org.jboss.seam.test.InterpolatorTest.testFail()</methodname> would fail when it should have passed. This issue has been rectified by changing the expected date of the test method to what the Java Virtual Machine (JVM) provides for a US locale.
 				</para>
 			</listitem>
@@ -300,6 +337,11 @@
 			</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>
+			<listitem>
+				<para>
 					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1083">JBPAPP-1083</ulink>: Outer join support should be added for aliases of the <classname>DetachedCriteria</classname> class. To do this, the following methods have been added to the class:
 				</para>
 				<itemizedlist>
@@ -397,6 +439,16 @@
 			</listitem>
 			<listitem>
 				<para>
+					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-940">JBPAPP-940</ulink>: The hibernate tests <code>org.hibernate.test.jpa.lock.JPALockTest</code> and <code>org.hibernate.test.tm.CMTTest</code> would not conclude when executed on a DB2 server. To overcome this problem, the method <methodname>doesReadCommittedCauseWritersToBlockReaders()</methodname>, which returns true if executed correctly, has been added to DB2Dialect in order to override Dialect's default settings.
+				</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>
+			<listitem>
+				<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.
 				</para>
 			</listitem>

Modified: projects/docs/enterprise/4.3.3/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Installation_Guide/en-US/Getting_Started.xml	2008-10-03 00:36:49 UTC (rev 79050)
+++ projects/docs/enterprise/4.3.3/Installation_Guide/en-US/Getting_Started.xml	2008-10-03 02:00:47 UTC (rev 79051)
@@ -240,7 +240,7 @@
 		<section id="Pre_Requisites-Configuring_Your_Java_Environment">
 			<title>Configuring Your Java Environment</title>
 			<para>
-				You must have a working installation of <emphasis role="bold">JDK 1.5</emphasis> before you install &JBEAP;. You can install the 32-bit or 64-bit JVM as per your requirements. In this guide we will show you how to install a 32-bit Sun JDK 5.0 on a Linux Platform and Microsoft Windows Platform. But before we do that let's take a look at some of the benefits of using a 64-bit JVM.
+				You must have a working installation of <emphasis role="bold">JDK 1.5</emphasis> before you install &JBEAP;. You can install the 32-bit or 64-bit JVM as per your requirements. In this guide we will show you how to install a 32-bit Sun JDK 5.0 using RHN, on a generic Linux Platform and Microsoft Windows Platform But before we do that let's take a look at some of the benefits of using a 64-bit JVM.
 				<itemizedlist id="Configuring_Your_Java_Environment-Benefits_of_64_bit_JVM_on_64_bit_OS_and_Hardware">
 					<title>Benefits of 64-bit JVM on 64-bit OS and Hardware:</title>
 					<listitem>
@@ -264,10 +264,59 @@
 						</para>
 					</listitem>
 				</itemizedlist>
-				<itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_on_Linux">
-					<title>Installing and Configuring 32-bit Sun JDK 5.0 on Linux</title>
+				<itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_using_RHN">
+					<title>Installing and Configuring 32-bit Sun JDK 5.0 using RHN</title>
 					<listitem>
 						<para>
+							Java SDKs are provided by the Red Hat Enterprise Linux 5  Supplementary channel for your Linux variant and architecture. Depending on the architecture, the channel names are:
+						</para>
+						<para>
+							rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementary-5
+						</para>
+						<para>
+							The <command moreinfo="none">java-1.5.0-bea</command>,
+							<command moreinfo="none">java-1.5.0-ibm</command> and
+							<command moreinfo="none">java-1.5.0-sun</command> SDKs are available from
+							these channels. Make sure you also install the
+							<command moreinfo="none">-devel</command> subpackages.
+						</para>
+					</listitem>
+					
+					<listitem>
+						<para>
+							Selecting <command moreinfo="none">alternatives</command> for <command moreinfo="none">java</command>, <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.5.0</command> (setting <command moreinfo="none">java_sdk_1.5.0</command> is optional). 
+						</para>
+						
+						<para>
+							This is only needed if you want to use the SysV service script
+							and/or want this installed SDK to be the default java and javac
+							in the system. This choice can often be overridden by setting
+							the <command moreinfo="none">JAVA_HOME</command> environment variable.
+						</para>
+						
+						<para>
+							The <command moreinfo="none">alternatives</command> system allows different versions of Java, from different sources to co-exist on your system. You should make sure the desired one is selected so that the service script uses the one you want.
+						</para>
+						
+						<para>
+							As root, issue the following command:
+						</para>
+						<screen>
+							<command moreinfo="none">/usr/sbin/alternatives --config java</command>
+						</screen>
+						<para>
+							and make sure the desired one is selected (marked with a '+'), or select it by entering its number as prompted.
+						</para>
+						
+						<para>
+							Make sure you do the same for <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.5.0.</command> We recommend that all point to the same manufacturer and version.
+						</para>
+					</listitem>
+				</itemizedlist>
+				<itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_on_a_generic_Linux_platform">
+					<title>Installing and Configuring 32-bit Sun JDK 5.0 on a generic Linux platform</title>
+					<listitem>
+						<para>
 							Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun&#39;s website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp"></ulink>. Choose "JDK 5.0 Update &lt;x&gt;" (where x is the latest update number) for download and then select "RPM in self-extracting" file for Linux<footnote><para>Make sure you choose the appropriate file for your platform.</para></footnote>. Read the instructions on Sun&#39;s website for installing the JDK.
 						</para>
 					</listitem>

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-03 00:36:49 UTC (rev 79050)
+++ projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml	2008-10-03 02:00:47 UTC (rev 79051)
@@ -271,16 +271,18 @@
 		<para>
 			Following is a list of issues fixed in this release:
 		</para>
-	<!--	<formalpara>
+		<formalpara>
 			<title>JBoss Messaging</title>
 			<para>
 			<itemizedlist>
 				<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>
@@ -291,16 +293,18 @@
 				</itemizedlist>
 			</para>
 		</formalpara> -->
-	<!--	<formalpara>
+		<formalpara>
 			<title>JBoss Remoting</title>
 			<para>
 				<itemizedlist>
 					<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>
 				</itemizedlist> 
 			</para>
-		</formalpara> -->
+		</formalpara>
 		<formalpara>
 			<title>JBoss Web</title>
 				<para>
@@ -319,6 +323,11 @@
 				<itemizedlist>
 					<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>
+					<listitem>
+						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-919">JBPAPP-919</ulink>: The Web Services stack was not able to be fully initialized and thus the first <methodname>webmethod </methodname> call is slow. In this latest version of the EAP, the Web Services stack is fully initialized. 
 						</para>
 					</listitem>
@@ -336,6 +345,11 @@
 					</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>
+					<listitem>
+						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1053">JBPAPP-1053</ulink>:  Seam icefaces would generate an error stipulating that an instance of the <code>compiler.ExpressionFactory</code> feature could not be achieved. In this release, the application deploys successfully and without the instance issue.
 						</para>
 					</listitem>
@@ -464,6 +478,11 @@
 				<itemizedlist>
 					<listitem>
 						<para>
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1217">JBPAPP-1217</ulink>: The Installation Guide did not provide correct information on how a Red Hat Enterprise Linux customer would install or update their Java JDK using Red Hat Network (RHN). This necessary information has now been included and the distinction made between the Red Hat Enterprise Linux customer Java installation method and installing Java on a generic Linux distribution. 
+						</para>
+					</listitem>
+					<listitem>
+						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1203">JBPAPP-1203</ulink>: In previous versions of the Server Configuration Guide and the Getting Started Guide, the properties <property>ha-local-tx-datasource</property> and <property>ha-xa-datasource</property> as well as their respective packages <package>jboss-ha-local-jdbc.rar</package> and <package>jboss-ha-xa-jdbc.rar</package> were listed as experimental when this is no longer the case. This updated CP documentation now exludes the wording of <emphasis>experimental</emphasis> so that there is no confusion. 
 						</para>
 					</listitem>
@@ -484,6 +503,11 @@
 					</listitem>
 					<listitem>
 						<para>
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-754">JBPAPP-754</ulink>: Included in prior EAP distributions was an outdated Seam <filename>changelog.txt</filename> file which acted as Seam release notes. As all EAP fixes for mention in the release notes are included in such, this file became irrelevant and outdated. With this new CP release, this file is no longer included. 
+						</para>
+					</listitem>
+					<listitem>
+						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-730">JBPAPP-730</ulink>: The Clustering Section of the Server Configuration Guide needed to be updated with the latest information relevant to the EAP. To rectify this issue, the updated community clustering section (along with information from the relevant wiki) has replaced the outdated information.
 						</para>
 					</listitem>
@@ -491,6 +515,34 @@
 			</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:
+				<itemizedlist>
+					<listitem>
+						<para>
+							removeTimerService (variation 2)
+						</para>
+					</listitem>
+					<listitem>
+						<para>
+							removeTimerService (variation 3)
+						</para>
+					</listitem>
+					<listitem>
+						<para>
+							String listTimers
+						</para>
+					</listitem>
+				</itemizedlist>
+				<note>
+					<para>
+						Variation numbering is based upon when each method appears in the code.
+					</para>
+				</note>
+			</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.




More information about the jboss-cvs-commits mailing list