[jboss-cvs] JBossAS SVN: r80235 - in projects/docs/enterprise: 4.2.5/Hibernate/Advanced_Topics/en-US and 13 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Oct 30 00:08:34 EDT 2008
Author: irooskov at redhat.com
Date: 2008-10-30 00:08:34 -0400 (Thu, 30 Oct 2008)
New Revision: 80235
Modified:
projects/docs/enterprise/4.2.5/Getting_Started/en-US/Author_Group.xml
projects/docs/enterprise/4.2.5/Getting_Started/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Hibernate/Advanced_Topics/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Hibernate/Annotations_Reference_Guide/en-US/Author_Group.xml
projects/docs/enterprise/4.2.5/Hibernate/Annotations_Reference_Guide/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Hibernate/Data_Access_Basics/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Hibernate/Data_Query/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Hibernate/Entity_Manager_User_Guide/en-US/Author_Group.xml
projects/docs/enterprise/4.2.5/Hibernate/Entity_Manager_User_Guide/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Hibernate/Getting_Started/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Hibernate/Object_Relational_Mapping/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Hibernate/Object_Relational_Mapping/en-US/Inheritance_Mapping.xml
projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Author_Group.xml
projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Inheritance_Mapping.xml
projects/docs/enterprise/4.2.5/Hibernate/Tools_And_Examples/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Author_Group.xml
projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Seam/Reference_Guide/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Author_Group.xml
projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml
projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Server_Configuration_Guide_CP05.xml
projects/docs/enterprise/4.2.5/readme/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml
projects/docs/enterprise/4.3.3/readme/en-US/Book_Info.xml
projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml
Log:
updated 4.3.3 release notes with JBPAPP-920 and those related to it. Also updated Author Group files of 4.2.5 books in able to build PDFs in new publican build system
Modified: projects/docs/enterprise/4.2.5/Getting_Started/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Getting_Started/en-US/Author_Group.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Getting_Started/en-US/Author_Group.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -2,4 +2,9 @@
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<authorgroup><corpauthor> Red Hat Documentation Group </corpauthor></authorgroup>
+<authorgroup>
+<author>
+ <firstname>Red Hat Documentation Group</firstname>
+ <surname></surname>
+ </author>
+</authorgroup>
Modified: projects/docs/enterprise/4.2.5/Getting_Started/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Getting_Started/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Getting_Started/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo id="Getting_Started_JBoss_Enterprise_Application_Platform">
<title>Getting Started Guide CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>6</pubsnumber>
<productname>JBoss Application Server</productname>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Advanced_Topics/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Advanced_Topics/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Advanced_Topics/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo>
<title>Hibernate Advanced Topics CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Annotations_Reference_Guide/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Annotations_Reference_Guide/en-US/Author_Group.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Annotations_Reference_Guide/en-US/Author_Group.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -2,4 +2,9 @@
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<authorgroup><corpauthor> Red Hat Documentation Group </corpauthor></authorgroup>
+<authorgroup>
+<author>
+ <firstname>Red Hat Documentation Group</firstname>
+ <surname></surname>
+ </author>
+</authorgroup>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Annotations_Reference_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Annotations_Reference_Guide/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Annotations_Reference_Guide/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo id="Hibernate_Annotations_Reference_Guide">
<title>Hibernate Annotations Reference Guide CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Data_Access_Basics/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Data_Access_Basics/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Data_Access_Basics/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo>
<title>Hibernate Data Access Basics CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Data_Query/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Data_Query/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Data_Query/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo>
<title>Hibernate Data Query CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Entity_Manager_User_Guide/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Entity_Manager_User_Guide/en-US/Author_Group.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Entity_Manager_User_Guide/en-US/Author_Group.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -2,4 +2,9 @@
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<authorgroup><corpauthor> Red Hat Documentation Group </corpauthor></authorgroup>
+<authorgroup>
+<author>
+ <firstname>Red Hat Documentation Group</firstname>
+ <surname></surname>
+ </author>
+</authorgroup>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Entity_Manager_User_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Entity_Manager_User_Guide/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Entity_Manager_User_Guide/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo id="Hibernate_EntityManager">
<title>Hibernate Entity Manager User Guide CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application</productname>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Getting_Started/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Getting_Started/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Getting_Started/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo>
<title>Hibernate Getting Started Guide CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Object_Relational_Mapping/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Object_Relational_Mapping/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Object_Relational_Mapping/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo>
<title>Hibernate Object Relational Mapping CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Object_Relational_Mapping/en-US/Inheritance_Mapping.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Object_Relational_Mapping/en-US/Inheritance_Mapping.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Object_Relational_Mapping/en-US/Inheritance_Mapping.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -410,7 +410,7 @@
</para>
<table frame="topbot">
<title>Features of inheritance mappings</title>
- <tgroup cols='8' align='left' colsep='1' rowsep='1'>
+ <tgroup cols='9' align='left' colsep='1' rowsep='1'>
<colspec colname='c1' colwidth="1*"/>
<colspec colname='c2' colwidth="1*"/>
<colspec colname='c3' colwidth="1*"/>
@@ -419,6 +419,7 @@
<colspec colname='c6' colwidth="1*"/>
<colspec colname='c7' colwidth="1*"/>
<colspec colname='c8' colwidth="1*"/>
+ <colspec colname='c9' colwidth="1*"/>
<thead>
<row>
<entry>Inheritance strategy</entry>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Author_Group.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Author_Group.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -2,4 +2,9 @@
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<authorgroup><corpauthor> Red Hat Documentation Group </corpauthor></authorgroup>
+<authorgroup>
+<author>
+ <firstname>Red Hat Documentation Group</firstname>
+ <surname></surname>
+ </author>
+</authorgroup>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo id="Hibernate_Reference_Guide">
<title>Hibernate Reference Guide CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Inheritance_Mapping.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Inheritance_Mapping.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Reference_Guide/en-US/Inheritance_Mapping.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -310,7 +310,7 @@
</para>
<table frame="topbot" id="Limitations-Features_of_inheritance_mappings">
<title>Features of inheritance mappings</title>
- <tgroup align="left" cols="8" colsep="1" rowsep="1">
+ <tgroup align="left" cols="9" colsep="1" rowsep="1">
<colspec colname="c1" colwidth="1*"></colspec>
<colspec colname="c2" colwidth="1*"></colspec>
<colspec colname="c3" colwidth="1*"></colspec>
@@ -319,6 +319,7 @@
<colspec colname="c6" colwidth="1*"></colspec>
<colspec colname="c7" colwidth="1*"></colspec>
<colspec colname="c8" colwidth="1*"></colspec>
+ <colspec colname="c9" colwidth="1*"></colspec>
<thead>
<row>
<entry>
Modified: projects/docs/enterprise/4.2.5/Hibernate/Tools_And_Examples/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Hibernate/Tools_And_Examples/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Hibernate/Tools_And_Examples/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo>
<title>Hibernate Tools and Examples CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
Modified: projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Author_Group.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Author_Group.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -2,4 +2,9 @@
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<authorgroup><corpauthor> Red Hat Documentation Group </corpauthor></authorgroup>
+<authorgroup>
+<author>
+ <firstname>Red Hat Documentation Group</firstname>
+ <surname></surname>
+ </author>
+</authorgroup>
Modified: projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Installation_Guide/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,7 +4,7 @@
<bookinfo id="Installation_Guide_JBoss_Enterprise_Application_Platform">
<title>Installation Guide CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>6</pubsnumber>
<productname>JBoss Application Server</productname>
Modified: projects/docs/enterprise/4.2.5/Seam/Reference_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Seam/Reference_Guide/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Seam/Reference_Guide/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -3,7 +3,7 @@
]>
<bookinfo id="Seam_Reference_Guide-Seam___Contextual_Components">
<title>Seam Reference Guide CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>6</pubsnumber>
<productname>Seam</productname>
Modified: projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Author_Group.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Author_Group.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -2,4 +2,9 @@
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<authorgroup><corpauthor> Red Hat Documentation Group </corpauthor></authorgroup>
+<authorgroup>
+<author>
+ <firstname>Red Hat Documentation Group</firstname>
+ <surname></surname>
+ </author>
+</authorgroup>
Modified: projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -3,7 +3,7 @@
]>
<bookinfo id="Configuration_Guide-JBoss_Enterprise_Application_Platform">
<title>Server Configuration Guide CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>6</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
Modified: projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -554,202 +554,45 @@
</para>
<programlisting><Valve className="org.jboss.web.tomcat.tc5.sso.ClusteredSingleSignOn" /></programlisting>
</section>
-
- <section><title>Clustered Singleton Services</title>
- <para>A clustered singleton service (also known as an HA singleton) is a service that is deployed on multiple nodes in a cluster, but is providing its service on only one of the nodes. The node running the singleton service is typically called the master node. When the master fails or is shut down, another master is selected from the remaining nodes and the service is restarted on the new master. Thus, other than a brief interval when one master has stopped and another has yet to take over, the service is always being provided by one but only one node.
- </para>
- <figure id="master_node_fail.fig">
- <title>Topology after the Master Node fails</title>
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="images/master_node_fail.png"/>
- </imageobject>
- </mediaobject>
- </figure>
+ <section id="clustering-http-notification_policy">
+ <title>Clustered Session Notification Policy</title>
+ <para>
+ This section introduces the concept of a clustered session notification policy for determining whether the servlet spec notifications related to session events are allowed to be emitted on the local cluster node. Such notifications are emitted to implementations of the <package>javax.servlet.http.HttpSessionListener</package>, <package>javax.servlet.http.HttpSessionAttributeListener</package>, and <package>javax.servlet.http.HttpSessionBindingListener interfaces</package>.</para>
- <para>
- The JBoss Application Server (AS) provides support for a number of strategies for helping you deploy clustered singleton services. In this section we will explore the different strategies. All of the strategies are built on top of the HAPartition service described in the introduction. They rely on the <literal>HAPartition</literal> to provide notifications when different nodes in the cluster start and stop; based on those notifications each node in the cluster can independently (but consistently) determine if it is now the master node and needs to begin providing a service.
+ <para>
+ This new notification policy concept is defined in the <package>org.jboss.web.tomcat.service.session.notification</package> Java package, and all classes referenced below are a part of this package. </para>
+ <para>
+ While it is possible to implement <classname>ClusteredSessionNotificationPolicy</classname> for case-specific customization, JBoss provides <classname>LegacyClusteredSessionNotificationPolicy</classname>, which implements the behavior in previous JBoss versions (the default), and <classname>IgnoreUndeployLegacyClusteredSessionNotificationPolicy</classname>, which implements the same behavior except for undeployment situations in which no <classname>HttpSessionListener</classname> and <classname>HttpSessionAttributeListener</classname> notifications are sent.
</para>
-
-
- <section><title>HASingletonDeployer service</title>
- <para>
- The simplest and most commonly used strategy for deploying an HA singleton is to take an ordinary deployment (war, ear, jar, whatever you would normally put in deploy) and deploy it in the <literal>$JBOSS_HOME/server/all/deploy-hasingleton</literal> directory instead of in <literal>deploy</literal>. The <literal>deploy-hasingleton</literal> directory does not lie under deploy or farm, so its contents are not automatically deployed when an AS instance starts. Instead, deploying the contents of this directory is the responsibility of a special service, the <literal>jboss.ha:service=HASingletonDeployer</literal> MBean (which itself is deployed via the deploy/deploy-hasingleton-service.xml file.) The HASingletonDeployer service is itself an HA Singleton, one whose provided service when it becomes master is to deploy the contents of deploy-hasingleton and whose service when it stops being the master (typically at server shutdown) is to undeploy the contents of <lit!
eral>deploy-hasingleton</literal>.
- </para>
- <para>
- So, by placing your deployments in <literal>deploy-hasingleton</literal> you know that they will be deployed only on the master node in the cluster. If the master node cleanly shuts down, they will be cleanly undeployed as part of shutdown. If the master node fails or is shut down, they will be deployed on whatever node takes over as master.
- </para>
- <para>Using deploy-hasingleton is very simple, but it does have two drawbacks:</para>
-
- <itemizedlist>
- <listitem>
- <para>There is no hot-deployment feature for services in <literal>deploy-hasingleton</literal>. Redeploying a service that has been deployed to <literal>deploy-hasingleton</literal> requires a server restart.
- </para>
- </listitem>
-
- <listitem>
- <para>If the master node fails and another node takes over as master, your singleton service needs to go through the entire deployment process before it will be providing services. Depending on how complex the deployment of your service is and what sorts of startup activities it engages in, this could take a while, during which time the service is not being provided.
- </para>
- </listitem>
-
- <!-- <listitem>
- <para>
- </para>
- </listitem>-->
- </itemizedlist>
-
- </section>
-
- <section><title>Mbean deployments using HASingletonController</title>
<para>
- If your service is an Mbean (i.e., not a J2EE deployment like an ear or war or jar), you can deploy it along with a service called an HASingletonController in order to turn it into an HA singleton. It is the job of the HASingletonController to work with the HAPartition service to monitor the cluster and determine if it is now the master node for its service. If it determines it has become the master node, it invokes a method on your service telling it to begin providing service. If it determines it is no longer the master node, it invokes a method on your service telling it to stop providing service. Let's walk through an illustration.
+ It is possible to change from the default <classname>LegacyClusteredSessionNotificationPolicy</classname> to <classname>IgnoreUndeployLegacyClusteredSessionNotificationPolicy</classname> or to a custom <classname>ClusteredSessionNotificationPolicy</classname> implementation by performing one of the following steps:
</para>
- <para>First, we have an MBean service that we want to make an HA singleton. The only thing special about it is it needs to expose in its MBean interface a method that can be called when it should begin providing service, and another that can be called when it should stop providing service:
- </para>
-
-<programlisting><![CDATA[
-public class HASingletonExample
-implements HASingletonExampleMBean {
-
-private boolean isMasterNode = false;
-
-public void startSingleton() {
-isMasterNode = true;
-}
-.
-public boolean isMasterNode() {
-return isMasterNode;
- }
-
- public void stopSingleton() {
- isMasterNode = false;
- }
-} ]]>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Using the system property 'jboss.web.clustered.session.notification.policy' and setting it equal to the class name of the policy you want to choose. This will change the policy for all web applications deployed in the application server.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Using jboss-web.xml to set the policy per application using the following format:
+ </para>
+<programlisting>
+<replication-config>
+ <session-notification-policy>
+ CLASS-NAME-HERE
+ </session-notification-policy>
+</replication-config>
</programlisting>
+ </listitem>
+ </itemizedlist>
-<para>
- We used “startSingleton” and “stopSingleton” in the above example, but you could name the methods anything.
-</para>
-<para>
- Next, we deploy our service, along with an HASingletonController to control it, most likely packaged in a .sar file, with the following <literal>META-INF/jboss-service.xml</literal>:
-</para>
-<programlisting><![CDATA[
- <server>
- <!-- This MBean is an example of a clustered singleton -->
- <mbean code="org.jboss.ha.examples.HASingletonExample"
- name=“jboss:service=HASingletonExample"/>
-
- <!-- This HASingletonController manages the cluster Singleton -->
- <mbean code="org.jboss.ha.singleton.HASingletonController"
- name="jboss:service=ExampleHASingletonController">
-
- <!-- Inject a ref to the HAPartition -->
- <depends optional-attribute-name="ClusterPartition" proxy-type="attribute">
- jboss:service=${jboss.partition.name:DefaultPartition}
- </depends>
- <!-- Inject a ref to the service being controlled -->
- <depends optional-attribute-name="TargetName">
- jboss:service=HASingletonExample
- </depends>
- <!-- Methods to invoke when become master / stop being master -->
- <attribute name="TargetStartMethod">startSingleton</attribute>
- <attribute name="TargetStopMethod">stopSingleton</attribute>
- </mbean>
-</server> ]]>
-</programlisting>
-
-<para>Voila! A clustered singleton service.
-</para>
-<para>
- The obvious downside to this approach is it only works for MBeans. Upsides are that the above example can be placed in <literal>deploy</literal> or <literal>farm</literal> and thus can be hot deployed and farmed deployed. Also, if our example service had complex, time-consuming startup requirements, those could potentially be implemented in create() or start() methods. JBoss will invoke create() and start() as soon as the service is deployed; it doesn't wait until the node becomes the master node. So, the service could be primed and ready to go, just waiting for the controller to implement startSingleton() at which point it can immediately provide service.
-</para>
-<para>
- The jboss.ha:service=HASingletonDeployer service discussed above is itself an interesting example of using an HASingletonController. Here is its deployment descriptor (extracted from the <literal>deploy/deploy-hasingleton-service.xml</literal> file):
-</para>
-<programlisting><![CDATA[
-<mbean code="org.jboss.ha.singleton.HASingletonController"
-name="jboss.ha:service=HASingletonDeployer">
- <depends optional-attribute-name="ClusterPartition" proxy-type="attribute">
- jboss:service=${jboss.partition.name:DefaultPartition}
- </depends>
- <depends optional-attributeame="TargetName">
- jboss.system:service=MainDeployer
- </depends>
- <attribute name="TargetStartMethod">deploy</attribute>
- <attribute name="TargetStartMethodArgument">
- ${jboss.server.home.url}/deploy-hasingleton
- </attribute>
- <attribute name="TargetStopMethod">undeploy</attribute>
- <attribute name="TargetStopMethodArgument">
- ${jboss.server.home.url}/deploy-hasingleton
- </attribute>
-</mbean> ]]>
-</programlisting>
-
-<para>
- A few interesting things here. First the service being controlled is the <literal>MainDeployer</literal> service, which is the core deployment service in JBoss. That is, it's a service that wasn't written with an intent that it be controlled by an <literal>HASingletonController</literal>. But it still works! Second, the target start and stop methods are “deploy” and “undeploy”. No requirement that they have particular names, or even that they logically have “start” and “stop” functionality. Here the functionality of the invoked methods is more like “do” and “undo”. Finally, note the “<literal>TargetStart(Stop)MethodArgument</literal>” attributes. Your singleton service's start/stop methods can take an argument, in this case the location of the directory the <literal>MainDeployer</literal> should deploy/undeploy.
-</para>
-
-
+ <note>
+ <para>
+ The session-notification-policy element shown above is not part of the official DTD for a JBoss 4.2+ jboss-web.xml (see <ulink url="http://www.jboss.org/j2ee/dtd/jboss-web_4_2.dtd">http://www.jboss.org/j2ee/dtd/jboss-web_4_2.dtd</ulink>). However, the internal jboss-web.xml parsing logic will properly handle the element in JBoss AS 4.2.4 and later as well was in EAP 4.2.0.GA_CP05 and 4.3.0.GA_CP03 and later.
+ </para>
+ </note>
</section>
-
-
- <section><title>HASingleton deployments using a Barrier</title>
- <para>Services deployed normally inside deploy or farm that want to be started/stopped whenever the content of deploy-hasingleton gets deployed/undeployed, (i.e., whenever the current node becomes the master), need only specify a dependency on the Barrier mbean:
- </para>
-<programlisting><![CDATA[<depends>jboss.ha:service=HASingletonDeployer,type=Barrier</depends>]]>
-</programlisting>
-
-<para>
- The way it works is that a BarrierController is deployed along with the jboss.ha:service=HASingletonDeployer MBean and listens for JMX notifications from it. A BarrierController is a relatively simple Mbean that can subscribe to receive any JMX notification in the system. It uses the received notifications to control the lifecycle of a dynamically created Mbean called the Barrier.The Barrier is instantiated, registered and brought to the CREATE state when the BarrierController is deployed. After that, the BarrierController starts and stops the Barrier when matching JMX notifications are received. Thus, other services need only depend on the Barrier MBean using the usual <depends> tag, and they will be started and stopped in tandem with the Barrier. When the BarrierController is undeployed the Barrier is destroyed too.
-</para>
-<para> This provides an alternative to the deploy-hasingleton approach in that we can use farming to distribute the service, while content in deploy-hasingleton must be copied manually on all nodes.
-</para>
-
-<para>
- On the other hand, the barrier-dependent service will be instantiated/created (i.e., any create() method invoked) on all nodes, but only started on the master node. This is different with the deploy-hasingleton approach that will only deploy (instantiate/create/start) the contents of the deploy-hasingleton directory on one of the nodes.
-</para>
-
-<para>So services depending on the barrier will need to make sure they do minimal or no work inside their create() step, rather they should use start() to do the work.
-</para>
-
-<note><title>Note</title>
- <para>The Barrier controls the start/stop of dependent services, but not their destruction, which happens only when the <literal>BarrierController</literal> is itself destroyed/undeployed. Thus using the <literal>Barrier</literal> to control services that need to be "destroyed" as part of their normal “undeploy” operation (like, for example, an <literal>EJBContainer</literal>) will not have the desired effect.
-</para>
-</note>
-
-
-
-</section>
-
-
-<section><title>Determining the master node</title>
- <para>The various clustered singleton management strategies all depend on the fact that each node in the cluster can independently react to changes in cluster membership and correctly decide whether it is now the “master node”. How is this done?
- </para>
-
- <para>Prior to JBoss AS 4.2.0, the methodology for this was fixed and simple. For each member of the cluster, the HAPartition mbean maintains an attribute called the CurrentView, which is basically an ordered list of the current members of the cluster. As nodes join and leave the cluster, JGroups ensures that each surviving member of the cluster gets an updated view. You can see the current view by going into the JMX console, and looking at the CurrentView attribute in the <literal>jboss:service=DefaultPartition</literal> mbean. Every member of the cluster will have the same view, with the members in the same order.
- </para>
-
- <para>Let's say, for example, that we have a 4 node cluster, nodes A through D, and the current view can be expressed as {A, B, C, D}. Generally speaking, the order of nodes in the view will reflect the order in which they joined the cluster (although this is not always the case, and should not be assumed to be the case.)
- </para>
-
- <para>
- To further our example, let's say there is a singleton service (i.e., an <literal>HASingletonController</literal>) named Foo that's deployed around the cluster, except, for whatever reason, on B. The <literal>HAPartition</literal> service maintains across the cluster a registry of what services are deployed where, in view order. So, on every node in the cluster, the <literal>HAPartition</literal> service knows that the view with respect to the Foo service is {A, C, D} (no B).
- </para>
-
- <para>
- Whenever there is a change in the cluster topology of the Foo service, the <literal>HAPartition</literal> service invokes a callback on Foo notifying it of the new topology. So, for example, when Foo started on D, the Foo service running on A, C and D all got callbacks telling them the new view for Foo was {A, C, D}. That callback gives each node enough information to independently decide if it is now the master. The Foo service on each node does this by checking if they are the first member of the view – if they are, they are the master; if not, they're not. Simple as that.
- </para>
-
- <para>
- If A were to fail or shutdown, Foo on C and D would get a callback with a new view for Foo of {C, D}. C would then become the master. If A restarted, A, C and D would get a callback with a new view for Foo of {C, D, A}. C would remain the master – there's nothing magic about A that would cause it to become the master again just because it was before.
- </para>
-
-</section>
-
- </section>
-
-
</chapter>
Modified: projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Server_Configuration_Guide_CP05.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Server_Configuration_Guide_CP05.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/Server_Configuration_Guide/en-US/Server_Configuration_Guide_CP05.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -34,6 +34,7 @@
<xi:include href="Clustering_Guide_EJBs.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Clustering_Guide_Entity_EJBs.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Clustering_Guide_HTTP.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<xi:include href="Clustering_Guide_Clustered_Singleton_Services.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Clustering_Guide_JMS.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Clustering_Guide_JBoss_Cache_JGroups.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</part>
Modified: projects/docs/enterprise/4.2.5/readme/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/readme/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/readme/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -4,14 +4,14 @@
<articleinfo>
<title>Release Notes CP05</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 CP05</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 5</subtitle>
<edition>1.0</edition>
<pubsnumber>6</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
<productnumber>4.2</productnumber>
<abstract>
<para>
- These release notes contain important information related to JBoss Enterprise Application Platform 4.2.0.CP04 that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing JBoss Enterprise Application Platform 4.2.0.CP04.
+ These release notes contain important information related to JBoss Enterprise Application Platform 4.2.0.CP05 that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing JBoss Enterprise Application Platform 4.2.0.CP05.
</para>
</abstract>
<isbn>N/A</isbn>
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-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -337,6 +337,14 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1225">JBPAPP-1225</ulink>: A <exceptionname>javax.ejb.NoSuchEJBException</exceptionname> exception would occur after the <methodname>sfsb.remove()</methodname> method was called from within the <classname>HttpSessionListener</classname> class. This cluser-wide operation being executed would mean that when one node was shutdown the HttpDessions would still be available on the other nodes for fail over security, however the SFSB would be missing causing the mentioned exception that the stateful bean could not be found.
+ </para>
+ <para>
+ In order to address this issue, a clustered session notification policy has been created. For documentation that explains this, refer to section 16.11 of the Server Configuration Guide.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1218">JBPAPP-1218</ulink>: If an illegal character was entered into the JMX console search function, a 500 exception would be presented to a user isntead of an error message explaining the exception occurrance. With this latest EAP release, the JMX console search function now displays an error message when given a malformed string.
</para>
</listitem>
@@ -494,7 +502,7 @@
<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>
- <listitem>
+ <!-- <listitem>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1044">JBPAPP-1044</ulink>: When undeploying specific Seam examples after interaction, a Null Pointer Exception (NPE) would occur. The list of affect examples are:
</para>
@@ -528,7 +536,7 @@
<para>
In this currect release, the NPE no longer occurs.
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1042">JBPAPP-1042</ulink>: An empty file <filename>jboss-seam-1.2.1.AP-src.tar.gz</filename> was included in the distribution. In order to avoid confusion, this file has been removed for this release.
@@ -611,16 +619,16 @@
<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>
+ <!-- <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>
- <listitem>
+ </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>
+ </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.
@@ -916,6 +924,11 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1286">JBPAPP-1286</ulink>: Footnotes within documentation tables and lists do not appear within PDFs. This issue resides within FOP and currently no workaround exists. Where possible footnotes are not used in the circumstances mentioned, however in documents such as the Release Notes the web address of a JIRA is automaticly generated as a footnote and places a number beside that of the JIRA, referencing a footnote that does not appear.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-909">JBPAPP-909</ulink>: Within the Hibernate component of the EAP the HashMap and HashSet iteration order changed from past releases because of support for JDK 1.6. However this has meant that the order of columns in union clauses and union-subclasses has changed, generating a slight impact on the components performance.
</para>
</listitem>
Modified: projects/docs/enterprise/4.3.3/readme/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.3.3/readme/en-US/Book_Info.xml 2008-10-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.3.3/readme/en-US/Book_Info.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -11,7 +11,7 @@
<productnumber>4.3</productnumber>
<abstract>
<para>
- These release notes contain important information related to JBoss Enterprise Application Platform 4.3.0.CP02 that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing JBoss Enterprise Application Platform 4.3.0.CP02.
+ These release notes contain important information related to JBoss Enterprise Application Platform 4.3.0.CP03 that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing JBoss Enterprise Application Platform 4.3.0.CP03.
</para>
</abstract>
<isbn>N/A</isbn>
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-30 03:59:09 UTC (rev 80234)
+++ projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml 2008-10-30 04:08:34 UTC (rev 80235)
@@ -234,7 +234,7 @@
<itemizedlist>
<listitem>
<para>
- <filename>Installation Guide</filename> explains how to install and verify the installation of JBoss Enteprise Application Platform using different installation modes.
+ <filename>Installation Guide</filename> explains how to install and verify the installation of JBoss Enterprise Application Platform using different installation modes.
</para>
</listitem>
<listitem>
@@ -332,7 +332,7 @@
</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.
+ <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 operational.
</para>
</listitem>
</itemizedlist>
@@ -349,7 +349,7 @@
</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.
+ <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 sufficient memory is available to support buffer size increases.
</para>
</listitem>
<listitem>
@@ -371,12 +371,12 @@
<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.
+ <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 incoming 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-927">JBPAPP-927</ulink>: JBoss Web Services has been upgraded to version 2.0.1.SP2_CP04, fixing many issues and adding enchancements.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-927">JBPAPP-927</ulink>: JBoss Web Services has been upgraded to version 2.0.1.SP2_CP04, fixing many issues and adding enhancements.
</para>
</listitem>
<listitem>
@@ -403,7 +403,7 @@
</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.
+ <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 inclusive, 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>
@@ -416,7 +416,7 @@
<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>
- <listitem>
+ <!-- <listitem>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1044">JBPAPP-1044</ulink>: When undeploying specific Seam examples after interaction, a Null Pointer Exception (NPE) would occur. The list of affect examples are:
</para>
@@ -450,7 +450,7 @@
<para>
In this currect release, the NPE no longer occurs.
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1042">JBPAPP-1042</ulink>: An empty file <filename>jboss-seam-1.2.1.AP-src.tar.gz</filename> was included in the distribution. In order to avoid confusion, this file has been removed for this release.
@@ -490,12 +490,12 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1214">JBPAPP-1214</ulink>: The Hibernate core version has been upgraded to 3.2.4.SP1_CP06 that incorporates numerious fixes and enhancements.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1214">JBPAPP-1214</ulink>: The Hibernate core version has been upgraded to 3.2.4.SP1_CP06 that incorporates numerous fixes and enhancements.
</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.
+ <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 omits <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>
<listitem>
@@ -532,7 +532,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1064">JBPAPP-1064</ulink>: Select annotation tests within <classname>IndexedCollectionTest</classname> would fail due to a failure reguarding the foreign key constraint within MySQL. To fix this issue, after each test the transaction needs to be committed instead of rolled back. Within the <filename>testMapKeyToEntity.java</filename> file the following ammendment has been made in order to fix this issue:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1064">JBPAPP-1064</ulink>: Select annotation tests within <classname>IndexedCollectionTest</classname> would fail due to a failure reguarding the foreign key constraint within MySQL. To fix this issue, after each test the transaction needs to be committed instead of rolled back. Within the <filename>testMapKeyToEntity.java</filename> file the following amendment has been made in order to fix this issue:
</para>
<para>
The original code at the end of a test consisted of the following:
@@ -662,6 +662,21 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-79">JBPAPP-979</ulink>: Information on how to reclaim disc space because Microsoft SQL Server does not undertake this de-allocation automaticly, has been added to the JBoss Messaging User Guide.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-920">JBPAPP-920</ulink>: The JBoss Messaging User Guide was outdated in previous releases. This latest CP release, incorporates the User Guide appropriate with the included version of the JBoss Messaging component.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-871">JBPAPP-871</ulink>: A note concerning how MDB and JBM dead letter queues work with each other has been included in the JBoss Messaging documentation.
+ </para>
+ </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>
@@ -758,12 +773,12 @@
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-983">JBPAPP-983</ulink>: The JBoss Enterprise Application Platform 4.3 has been certified on DB2 versions 8.2 and 9.1.
</para>
</formalpara>
- <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.
</para>
- </formalpara>
+ </formalpara> -->
<formalpara>
<title>JBPAPP-526</title>
<para>
More information about the jboss-cvs-commits
mailing list