[jboss-cvs] JBoss Messaging SVN: r3211 - trunk/docs/userguide/en/modules.

[jboss-cvs-commits at lists.jboss.org]

Author: clebert.suconic at jboss.com
Date: 2007-10-19 13:27:43 -0400 (Fri, 19 Oct 2007)
New Revision: 3211

Modified:
   trunk/docs/userguide/en/modules/configuration.xml
Log:
http://jira.jboss.com/jira/browse/JBMESSAGING-1096 - Removing callback configuration from docs

Modified: trunk/docs/userguide/en/modules/configuration.xml
===================================================================
--- trunk/docs/userguide/en/modules/configuration.xml	2007-10-19 17:21:09 UTC (rev 3210)
+++ trunk/docs/userguide/en/modules/configuration.xml	2007-10-19 17:27:43 UTC (rev 3211)
@@ -1854,23 +1854,5 @@
       <para>See the chapter on installation for a description of how to set-up
       the service binding manager for JBoss Messaging</para>
    </section>
-   <section id="conf.callback">
-      <title>Configuring the callback</title>
-      <para>JBoss Messaging uses a callback mechanism from Remoting that needs
-      a Socket for callback operations. These socket properties are passed to
-      the server by a remote call when the connection is being estabilished.
-      As we said before we will support bidirectional protocols in future
-      releases.</para>
-      <para>By default JBoss Messaging will execute
-      InetAddress.getLocalHost().getHostAddress() to access your local host
-      IP, but in case you need to setup a different IP, you can define a
-      system property in your java arguments:</para>
-      <para>Use java -Djboss.messaging.callback.bind.address=YourHost - That
-      will determine the callBack host in your client.</para>
-      <para>The client port will be selected randomly for any non used port.
-      But if you defined -Djboss.messaging.callback.bind.port=NumericPort in
-      your System Properties that number is going to be used for the call back
-      client port.</para>
-   </section>
    <!-- End conf.callback -->
 </chapter>
\ No newline at end of file