[jboss-cvs] JBossAS SVN: r80097 - in projects/docs/enterprise/4.3.3: Installation_Guide/en-US and 3 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Oct 27 03:00:57 EDT 2008
Author: irooskov at redhat.com
Date: 2008-10-27 03:00:57 -0400 (Mon, 27 Oct 2008)
New Revision: 80097
Modified:
projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/Security_Configuration.xml
projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/Security_Features.xml
projects/docs/enterprise/4.3.3/Installation_Guide/en-US/Author_Group.xml
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml
projects/docs/enterprise/4.3.3/examples/jboss-messaging-examples/common/src/org/jboss/example/jms/common/ExampleSupport.java
projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml
Log:
updated books and CC guide
Modified: projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/Security_Configuration.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/Security_Configuration.xml 2008-10-27 06:50:13 UTC (rev 80096)
+++ projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/Security_Configuration.xml 2008-10-27 07:00:57 UTC (rev 80097)
@@ -64,7 +64,7 @@
<para>You must edit the file <filename>run.conf</filename> and uncomment the
lines indicated below to enable the Java Security Manager. Once those items are
- commented out from <filename>run.conf</filename>, simply start the server using the
+ uncommented from <filename>run.conf</filename>, simply start the server using the
supplied startup script (<filename>run.sh</filename> or <filename>run.bat</filename>)
as normal.</para>
Modified: projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/Security_Features.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/Security_Features.xml 2008-10-27 06:50:13 UTC (rev 80096)
+++ projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/Security_Features.xml 2008-10-27 07:00:57 UTC (rev 80097)
@@ -123,7 +123,7 @@
<para>If you need additional logging for web-based requests, uncomment
the <literal>AccessLogValve</literal> in
- <filename>deploy/jbossweb.deployer/server.xml</filename>. The access
+ <filename>deploy/jboss-web.deployer/server.xml</filename>. The access
log will be available in the <filename>log</filename> directory of the
server configuration.</para>
Modified: projects/docs/enterprise/4.3.3/Installation_Guide/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Installation_Guide/en-US/Author_Group.xml 2008-10-27 06:50:13 UTC (rev 80096)
+++ projects/docs/enterprise/4.3.3/Installation_Guide/en-US/Author_Group.xml 2008-10-27 07:00:57 UTC (rev 80097)
@@ -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.3.3/Server_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml 2008-10-27 06:50:13 UTC (rev 80096)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml 2008-10-27 07:00:57 UTC (rev 80097)
@@ -557,7 +557,7 @@
<section id="clustering-http-notification_policy">
<title>Clustered Session Notification Policy</title>
<para>
- This chapter 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>
+ 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>
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>
@@ -577,13 +577,13 @@
<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>
+<programlisting>
+<replication-config>
+ <session-notification-policy>
+ CLASS-NAME-HERE
+ </session-notification-policy>
+</replication-config>
+</programlisting>
</listitem>
</itemizedlist>
Modified: projects/docs/enterprise/4.3.3/examples/jboss-messaging-examples/common/src/org/jboss/example/jms/common/ExampleSupport.java
===================================================================
--- projects/docs/enterprise/4.3.3/examples/jboss-messaging-examples/common/src/org/jboss/example/jms/common/ExampleSupport.java 2008-10-27 06:50:13 UTC (rev 80096)
+++ projects/docs/enterprise/4.3.3/examples/jboss-messaging-examples/common/src/org/jboss/example/jms/common/ExampleSupport.java 2008-10-27 07:00:57 UTC (rev 80097)
@@ -21,9 +21,9 @@
/**
* @author <a href="mailto:ovidiu at feodorov.com">Ovidiu Feodorov</a>
- * @version <tt>$Revision: 3092 $</tt>
+ * @version <tt>$Revision: 5084 $</tt>
*
- * $Id: ExampleSupport.java 3092 2007-09-10 21:42:30Z clebert.suconic at jboss.com $
+ * $Id: ExampleSupport.java 5084 2008-10-07 19:37:19Z clebert.suconic at jboss.com $
*/
public abstract class ExampleSupport
{
@@ -150,6 +150,8 @@
catch(Throwable t)
{
t.printStackTrace();
+ System.out.println("");
+ System.out.println("Please verify if you have access to the server. If you are using JBossEAP maybe you don't have security access");
setFailure(true);
}
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-27 06:50:13 UTC (rev 80096)
+++ projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml 2008-10-27 07:00:57 UTC (rev 80097)
@@ -714,6 +714,15 @@
</para>
</formalpara>
<formalpara>
+ <title>JBPAPP-1225</title>
+ <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>
+ </formalpara>
+ <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>
+ <formalpara>
<title>JBPAPP-1218</title>
<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.
More information about the jboss-cvs-commits
mailing list