[jboss-cvs] JBossAS SVN: r96034 - in projects/docs/enterprise: 4.2.8/Server_Configuration_Guide/en-US and 2 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Nov 5 00:27:59 EST 2009
Author: laubai
Date: 2009-11-05 00:27:58 -0500 (Thu, 05 Nov 2009)
New Revision: 96034
Modified:
projects/docs/enterprise/4.2.8/Installation_Guide/en-US/Post_Installation.xml
projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml
projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/EJB3.xml
projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/J2EE_EJBs_On_JBOSS.xml
projects/docs/enterprise/4.3.7/Installation_Guide/en-US/Post_Installation.xml
projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml
projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/EJB3.xml
projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/J2EE_EJBs_On_JBOSS.xml
Log:
Edited 4.2.8 and 4.3.7 Server Config Guide for JBPAPP-1876, and Installation Guide for JBPAPP-1866.
Modified: projects/docs/enterprise/4.2.8/Installation_Guide/en-US/Post_Installation.xml
===================================================================
--- projects/docs/enterprise/4.2.8/Installation_Guide/en-US/Post_Installation.xml 2009-11-05 05:09:58 UTC (rev 96033)
+++ projects/docs/enterprise/4.2.8/Installation_Guide/en-US/Post_Installation.xml 2009-11-05 05:27:58 UTC (rev 96034)
@@ -108,7 +108,7 @@
It is also possible to disable authentication on specific services. All specified paths in the sections below are relative to <literal>$JBOSS_HOME</literal>.
</para>
<formalpara>
- <title>Disabling Authentication for JXM Console:</title>
+ <title>Disabling Authentication for JMX Console:</title>
<para>
To disable authentication for the JMX console, edit the following file and comment out the security-constraint section:
<programlisting>
Modified: projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml
===================================================================
--- projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml 2009-11-05 05:09:58 UTC (rev 96033)
+++ projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml 2009-11-05 05:27:58 UTC (rev 96034)
@@ -202,7 +202,7 @@
<para>The JNDI client needs to be aware of the HA-JNDI cluster. You can pass a list of JNDI servers (i.e., the nodes in the HA-JNDI cluster) to the <literal>java.naming.provider.url</literal> JNDI setting in the <literal>jndi.properties</literal> file. Each server node is identified by its IP address and the JNDI port number. The server nodes are separated by commas (see <xref linkend="clustering-jndi-jboss"/> for how to configure the servers and ports).</para>
<programlisting>
-java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100
+java.naming.provider.url=server1:1100,server2:1100,server3:1100,server4:1100
</programlisting>
<para>When initialising, the JNP client code will try to get in touch with each server node from the
list, one after the other, stopping as soon as one server has been reached. It will then download
Modified: projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/EJB3.xml
===================================================================
--- projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/EJB3.xml 2009-11-05 05:09:58 UTC (rev 96033)
+++ projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/EJB3.xml 2009-11-05 05:27:58 UTC (rev 96034)
@@ -492,7 +492,7 @@
<para>The jboss-app.xml file provides JBoss-specific deployment configuration for the EAR application. For instance, it can specify the deployment order of modules in the EAR, deploy JBoss-specific application modules in the EAR, such as SARs (Service ARchive for MBeans) and HARs (Hibernate ARchive for Hibernate objects), provide security domain and JMX MBeans that can be used with this application, etc. You can learn more about the possible attributes in jboss-app.xml in its DTD: http://www.jboss.org/j2ee/dtd/jboss-app_4_2.dtd.</para>
- <para>A common use case for jboss-app.xml is to configure whether this EAR file should be deployed in its own scoped classloader to avoid naming conflicts with other applications. If your EAR application is deployed in its own scoped classloader and it only has one persistence-unit defined in its EJB3 JARs, you will be able to use @PersistenceContext EntotyManager em to inject EntityManager to session beans without worrying about passing the persistence unit name to the @PersistenceContext annotation. The following jboss-app.xml specifies a scoped classloader myapp:archive=myapp.ear for the EAR application.</para>
+ <para>A common use case for jboss-app.xml is to configure whether this EAR file should be deployed in its own scoped classloader to avoid naming conflicts with other applications. If your EAR application is deployed in its own scoped classloader and it only has one persistence-unit defined in its EJB3 JARs, you will be able to use @PersistenceContext EntityManager em to inject EntityManager to session beans without worrying about passing the persistence unit name to the @PersistenceContext annotation. The following jboss-app.xml specifies a scoped classloader myapp:archive=myapp.ear for the EAR application.</para>
<programlisting>
<![CDATA[
Modified: projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/J2EE_EJBs_On_JBOSS.xml
===================================================================
--- projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/J2EE_EJBs_On_JBOSS.xml 2009-11-05 05:09:58 UTC (rev 96033)
+++ projects/docs/enterprise/4.2.8/Server_Configuration_Guide/en-US/J2EE_EJBs_On_JBOSS.xml 2009-11-05 05:27:58 UTC (rev 96034)
@@ -1144,7 +1144,7 @@
The <literal>web-class-loader</literal> element specifies a subclass of <literal>org.jboss.web.WebClassLoader</literal> that is used in conjunction with the <literal>WebService</literal> MBean to allow dynamic loading of resources and classes from deployed ears, EJB JARs and WARs. A <literal>WebClassLoader</literal> is associated with a <literal>Container</literal> and must have an <literal>org.jboss.mx.loading.UnifiedClassLoader</literal> as its parent. It overrides the <literal>getURLs()</literal> method to return a different set of URLs for remote loading than what is used for local loading.
</para>
<para>
- <literal>WebClaossLoader</literal> has two methods meant to be overridden by subclasses: <literal>getKey()</literal> and <literal>getBytes()</literal>. The latter is a no-op in this implementation and should be overridden by subclasses with bytecode generation ability, such as the classloader used by the iiop module.
+ <literal>WebClassLoader</literal> has two methods meant to be overridden by subclasses: <literal>getKey()</literal> and <literal>getBytes()</literal>. The latter is a no-op in this implementation and should be overridden by subclasses with bytecode generation ability, such as the classloader used by the iiop module.
</para>
<para>
<literal>WebClassLoader</literal> subclasses must have a constructor with the same signature as the <literal>WebClassLoader(ObjectName containerName, UnifiedClassLoader parent)</literal> constructor.
Modified: projects/docs/enterprise/4.3.7/Installation_Guide/en-US/Post_Installation.xml
===================================================================
--- projects/docs/enterprise/4.3.7/Installation_Guide/en-US/Post_Installation.xml 2009-11-05 05:09:58 UTC (rev 96033)
+++ projects/docs/enterprise/4.3.7/Installation_Guide/en-US/Post_Installation.xml 2009-11-05 05:27:58 UTC (rev 96034)
@@ -108,7 +108,7 @@
It is also possible to disable authentication on specific services. All specified paths in the sections below are relative to <literal>$JBOSS_HOME</literal>.
</para>
<formalpara>
- <title>Disabling Authentication for JXM Console:</title>
+ <title>Disabling Authentication for JMX Console:</title>
<para>
To disable authentication for the JMX console, edit the following file and comment out the security-constraint section:
<programlisting>
Modified: projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml
===================================================================
--- projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml 2009-11-05 05:09:58 UTC (rev 96033)
+++ projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/Clustering_Guide_JNDI.xml 2009-11-05 05:27:58 UTC (rev 96034)
@@ -202,7 +202,7 @@
<para>The JNDI client needs to be aware of the HA-JNDI cluster. You can pass a list of JNDI servers (i.e., the nodes in the HA-JNDI cluster) to the <literal>java.naming.provider.url</literal> JNDI setting in the <literal>jndi.properties</literal> file. Each server node is identified by its IP address and the JNDI port number. The server nodes are separated by commas (see <xref linkend="clustering-jndi-jboss"/> for how to configure the servers and ports).</para>
<programlisting>
-java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100
+java.naming.provider.url=server1:1100,server2:1100,server3:1100,server4:1100
</programlisting>
<para>When initialising, the JNP client code will try to get in touch with each server node from the
list, one after the other, stopping as soon as one server has been reached. It will then download
Modified: projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/EJB3.xml
===================================================================
--- projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/EJB3.xml 2009-11-05 05:09:58 UTC (rev 96033)
+++ projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/EJB3.xml 2009-11-05 05:27:58 UTC (rev 96034)
@@ -492,7 +492,7 @@
<para>The jboss-app.xml file provides JBoss-specific deployment configuration for the EAR application. For instance, it can specify the deployment order of modules in the EAR, deploy JBoss-specific application modules in the EAR, such as SARs (Service ARchive for MBeans) and HARs (Hibernate ARchive for Hibernate objects), provide security domain and JMX MBeans that can be used with this application, etc. You can learn more about the possible attributes in jboss-app.xml in its DTD: http://www.jboss.org/j2ee/dtd/jboss-app_4_2.dtd.</para>
- <para>A common use case for jboss-app.xml is to configure whether this EAR file should be deployed in its own scoped classloader to avoid naming conflicts with other applications. If your EAR application is deployed in its own scoped classloader and it only has one persistence-unit defined in its EJB3 JARs, you will be able to use @PersistenceContext EntotyManager em to inject EntityManager to session beans without worrying about passing the persistence unit name to the @PersistenceContext annotation. The following jboss-app.xml specifies a scoped classloader myapp:archive=myapp.ear for the EAR application.</para>
+ <para>A common use case for jboss-app.xml is to configure whether this EAR file should be deployed in its own scoped classloader to avoid naming conflicts with other applications. If your EAR application is deployed in its own scoped classloader and it only has one persistence-unit defined in its EJB3 JARs, you will be able to use @PersistenceContext EntityManager em to inject EntityManager to session beans without worrying about passing the persistence unit name to the @PersistenceContext annotation. The following jboss-app.xml specifies a scoped classloader myapp:archive=myapp.ear for the EAR application.</para>
<programlisting>
<![CDATA[
Modified: projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/J2EE_EJBs_On_JBOSS.xml
===================================================================
--- projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/J2EE_EJBs_On_JBOSS.xml 2009-11-05 05:09:58 UTC (rev 96033)
+++ projects/docs/enterprise/4.3.7/Server_Configuration_Guide/en-US/J2EE_EJBs_On_JBOSS.xml 2009-11-05 05:27:58 UTC (rev 96034)
@@ -1144,7 +1144,7 @@
The <literal>web-class-loader</literal> element specifies a subclass of <literal>org.jboss.web.WebClassLoader</literal> that is used in conjunction with the <literal>WebService</literal> MBean to allow dynamic loading of resources and classes from deployed ears, EJB JARs and WARs. A <literal>WebClassLoader</literal> is associated with a <literal>Container</literal> and must have an <literal>org.jboss.mx.loading.UnifiedClassLoader</literal> as its parent. It overrides the <literal>getURLs()</literal> method to return a different set of URLs for remote loading than what is used for local loading.
</para>
<para>
- <literal>WebClaossLoader</literal> has two methods meant to be overridden by subclasses: <literal>getKey()</literal> and <literal>getBytes()</literal>. The latter is a no-op in this implementation and should be overridden by subclasses with bytecode generation ability, such as the classloader used by the iiop module.
+ <literal>WebClassLoader</literal> has two methods meant to be overridden by subclasses: <literal>getKey()</literal> and <literal>getBytes()</literal>. The latter is a no-op in this implementation and should be overridden by subclasses with bytecode generation ability, such as the classloader used by the iiop module.
</para>
<para>
<literal>WebClassLoader</literal> subclasses must have a constructor with the same signature as the <literal>WebClassLoader(ObjectName containerName, UnifiedClassLoader parent)</literal> constructor.
More information about the jboss-cvs-commits
mailing list