From jboss-remoting-commits at lists.jboss.org Wed May 13 01:56:06 2009 Content-Type: multipart/mixed; boundary="===============4758420829505945551==" MIME-Version: 1.0 From: jboss-remoting-commits at lists.jboss.org To: jboss-remoting-commits at lists.jboss.org Subject: [jboss-remoting-commits] JBoss Remoting SVN: r5211 - remoting2/branches/2.x/docs/guide/en. Date: Wed, 13 May 2009 01:47:42 -0400 Message-ID: --===============4758420829505945551== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: ron.sigal(a)jboss.com Date: 2009-05-13 01:47:42 -0400 (Wed, 13 May 2009) New Revision: 5211 Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml Log: JBREM-1121: Added section about configuring socket factories by the Invoker= Locator. Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- remoting2/branches/2.x/docs/guide/en/chap5.xml 2009-05-13 05:29:47 UTC = (rev 5210) +++ remoting2/branches/2.x/docs/guide/en/chap5.xml 2009-05-13 05:47:42 UTC = (rev 5211) @@ -220,7 +220,7 @@ = = -
+
Declarative configuration: MBeans = One configuration option discussed in Section
= -
+
Declarative configuration: POJOs = The last configuration option discussed in Section
= +
+ Client side configuration from the JBoss Application Server</= title> + = + <para>As described in sections <xref linkend=3D"section-declarative-= configuration-mbeans"/> + and <xref linkend=3D"section-declarative-configuration-pojos"/>, + the declarative xml files used by the Application Server can be used= to configure the = + client by way of the parameters included in the <classname>InvokerLo= cator</classname>. + However, a peculiarity in the way socket factories are created on th= e client = + restricts the parameters taken into consideration to those passed in= the = + configuration map passed to the <classname>org.jboss.remoting.Client= </classname> + constructor. The following two parameters, introduced in releases 2= .4.0.SP1 and + 2.5.2, respectively, eliminate that restriction.</para> + = + <para><emphasis role=3D"bold">org.jboss.remoting.Remoting.SOCKET_FAC= TORY_NAME</emphasis> (actual value + is 'socketFactory') - key for giving the name of the socket factory = class to be used + by clients.</para> + + <para><emphasis role=3D"bold">org.jboss.remoting.Remoting.USE_ALL_SO= CKET_FACTORY_PARAMS</emphasis> (actual value + is 'useAllSocketFactoryParams') - key for indicating that all socket= factory parameters + in the <classname>InvokerLocator</classname> should be used by clien= ts.</para> + = + <para>Note that the parameter <code>org.jboss.remoting.Remoting.CONF= IG_OVERRIDES_LOCATOR</code> + (actual value "configOverridesLocator"), described in section + <xref linkend=3D"section-org-jboss-remoting-Remoting"/>, is also rel= evant.</para> + </section> + = <section> <title>Socket creation listeners = @@ -5967,7 +5993,7 @@ =
= -
+
org.jboss.remoting.Remoting = CUSTOM_SERVER_SOCKET_FACTORY --===============4758420829505945551==--