[jboss-cvs] JBossAS SVN: r94538 - projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Oct 8 23:50:34 EDT 2009
Author: benlc
Date: 2009-10-08 23:50:34 -0400 (Thu, 08 Oct 2009)
New Revision: 94538
Modified:
projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/Book_Info.xml
projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/JBoss_Remoting_User_Guide.xml
projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/architecture.xml
projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/components.xml
projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/overview.xml
Log:
"minor changes following spellcheck"
Modified: projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/Book_Info.xml 2009-10-09 03:44:16 UTC (rev 94537)
+++ projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/Book_Info.xml 2009-10-09 03:50:34 UTC (rev 94538)
@@ -8,7 +8,7 @@
<productname>JBoss Enterprise Application Platform</productname>
<productnumber>5.0</productnumber>
<edition>1.0</edition>
- <pubsnumber>1</pubsnumber>
+ <pubsnumber>2</pubsnumber>
<abstract>
<para>This book serves as guide to the JBoss Enterpise Application Platform Remoting Project.</para>
</abstract>
Modified: projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/JBoss_Remoting_User_Guide.xml
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/JBoss_Remoting_User_Guide.xml 2009-10-09 03:44:16 UTC (rev 94537)
+++ projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/JBoss_Remoting_User_Guide.xml 2009-10-09 03:50:34 UTC (rev 94538)
@@ -9,6 +9,7 @@
<xi:include href="overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="architecture.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="components.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<!-- <xi:include href="remoting_libraries.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- <index /> -->
</book>
Modified: projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/architecture.xml
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/architecture.xml 2009-10-09 03:44:16 UTC (rev 94537)
+++ projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/architecture.xml 2009-10-09 03:50:34 UTC (rev 94538)
@@ -235,10 +235,10 @@
</figure>
<para>
- Once the invoker registry has created server invokers and a detector is created and started on the server, the detector will periodically pull the server invokers from the invoker registry. The detector will then use this information to publish a detection message containing the locator and the subsytems supported by each server invoker. The detection message is published by either a multicast broadcast or a binding into a Java Naming and Directory Interface (JNDI) server.
+ Once the invoker registry has created server invokers and a detector is created and started on the server, the detector will periodically pull the server invokers from the invoker registry. The detector will then use this information to publish a detection message containing the locator and the subsystems supported by each server invoker. The detection message is published by either a multicast broadcast or a binding into a Java Naming and Directory Interface (JNDI) server.
</para>
<para>
- The client detector will either recieve the multicast broadcast message or poll the JNDI server for detection messages. In the event that a detection message relates to a server which has recently appeared online, the detector will register the server in the network registry. A change to the network registry will also occur when a detector has discovered that a remoting server is no longer available and removes it from the registry. The network registry will announce a change to the registry by broadcasting a Java Management Extensions (JMX) notification.
+ The client detector will either receive the multicast broadcast message or poll the JNDI server for detection messages. In the event that a detection message relates to a server which has recently appeared online, the detector will register the server in the network registry. A change to the network registry will also occur when a detector has discovered that a remoting server is no longer available and removes it from the registry. The network registry will announce a change to the registry by broadcasting a Java Management Extensions (JMX) notification.
</para>
</section>
</chapter>
Modified: projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/components.xml
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/components.xml 2009-10-09 03:44:16 UTC (rev 94537)
+++ projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/components.xml 2009-10-09 03:50:34 UTC (rev 94538)
@@ -94,7 +94,7 @@
<row>
<entry><package>org.jboss.remoting.ident</package>.<classname>Identity</classname></entry>
<entry>
- An <classname>Identity</classname> object is one of the main components remoting uses during discovery to identify remoting server instances and is the means by which the uniqueness of remoting servers is guarenteed. If there are two remoting server instances running on the same server, they can be uniquely identified by their <varname>instanceID</varname>, which remains consistent between server reboots, and their <varname>JMXId</varname> which varies with each server reboot. At present, the Ids are maintained in the file system. The ability to identify a server which has encountered problems and has been restarted is important from a monitoring point of view.
+ An <classname>Identity</classname> object is one of the main components remoting uses during discovery to identify remoting server instances and is the means by which the uniqueness of remoting servers is guaranteed. If there are two remoting server instances running on the same server, they can be uniquely identified by their <varname>instanceID</varname>, which remains consistent between server reboots, and their <varname>JMXId</varname> which varies with each server reboot. At present, the Ids are maintained in the file system. The ability to identify a server which has encountered problems and has been restarted is important from a monitoring point of view.
</entry>
</row>
<row>
@@ -184,7 +184,7 @@
<itemizedlist>
<listitem>
<para>
- this method uses only the protocol, host and port for its comparison. The following code samples demonstate its use;
+ this method uses only the protocol, host and port for its comparison. The following code samples demonstrate its use;
<!-- </para>
<itemizedlist>
<listitem>
@@ -216,7 +216,7 @@
</section>
<section><title>Identity Points to Note</title>
<para>
- When creating the identity to be presisted, JBoss Remoting will attempt to write to the <filename>'jboss.identity'</filename> file according to the following sequence:
+ When creating the identity to be persisted, JBoss Remoting will attempt to write to the <filename>'jboss.identity'</filename> file according to the following sequence:
</para>
<orderedlist>
<listitem>
@@ -261,7 +261,7 @@
</orderedlist>
<important><title>Important</title>
<para>
- A RuntimeException will be thrown in the event that the 'jboss.identity' file cannot be created or modified. This will result in the detector producing errors during startup. More details in regard to maintaining the persistence of the identity and the location to which the identity is stored can be found in <package>org.jboss.remoting.ident.Identity</package>.<classname>createId()</classname>.
+ A RuntimeException will be thrown in the event that the 'jboss.identity' file cannot be created or modified. This will result in the detector producing errors during start-up. More details in regard to maintaining the persistence of the identity and the location to which the identity is stored can be found in <package>org.jboss.remoting.ident.Identity</package>.<classname>createId()</classname>.
</para>
</important>
</section>
@@ -312,7 +312,7 @@
</para>
-->
<para>
- Under normal circumstances, remote server detection is a passive operation causing events to be triggered as a result of the receipt of detection messages by the client detector. In some cases, the ability to synchronously discover the remoting servers that exist upon startup is required. This can be achieved by calling the <methodname>forceDetection()</methodname> method (defined and implemented in the <classname>AbstractDetector</classname> class) on the detector which will return an array of <classname>NetworkInstances</classname> objects containing the server information.
+ Under normal circumstances, remote server detection is a passive operation causing events to be triggered as a result of the receipt of detection messages by the client detector. In some cases, the ability to synchronously discover the remoting servers that exist upon start-up is required. This can be achieved by calling the <methodname>forceDetection()</methodname> method (defined and implemented in the <classname>AbstractDetector</classname> class) on the detector which will return an array of <classname>NetworkInstances</classname> objects containing the server information.
</para>
<note><title>Note</title>
<para>
@@ -433,7 +433,7 @@
</programlisting>
<note><title>Note</title>
<para>
- The transport factories are loaded following a request for a particular protocol type which is then passed to the <methodname>createClientInvoker()</methodname> method as part of the (<type>Map</type> <parameter>config</parameter>) paramater.
+ The transport factories are loaded following a request for a particular protocol type which is then passed to the <methodname>createClientInvoker()</methodname> method as part of the (<type>Map</type> <parameter>config</parameter>) parameter.
</para>
</note>
Modified: projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/overview.xml
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/overview.xml 2009-10-09 03:44:16 UTC (rev 94537)
+++ projects/docs/enterprise/5.0/JBoss_Remoting/JBoss_Remoting_User_Guide/en-US/overview.xml 2009-10-09 03:50:34 UTC (rev 94538)
@@ -106,7 +106,7 @@
</row>
<row>
<entry>Server Identification</entry>
- <entry>A simple url based identifier facilitates the identification and subsequent calls to remoting servers.</entry>
+ <entry>A simple URL based identifier facilitates the identification and subsequent calls to remoting servers.</entry>
</row>
<row>
<entry>Server Grouping</entry>
More information about the jboss-cvs-commits
mailing list