Author: ron.sigal(a)jboss.com
Date: 2009-05-16 19:12:20 -0400 (Sat, 16 May 2009)
New Revision: 5243
Modified:
remoting2/branches/2.2/docs/guide/en/chap5.xml
Log:
JBREM-1102: Added discussion of "passConfigMapToMarshalFactory".
Modified: remoting2/branches/2.2/docs/guide/en/chap5.xml
===================================================================
--- remoting2/branches/2.2/docs/guide/en/chap5.xml 2009-05-16 04:11:23 UTC (rev 5242)
+++ remoting2/branches/2.2/docs/guide/en/chap5.xml 2009-05-16 23:12:20 UTC (rev 5243)
@@ -3155,6 +3155,15 @@
is required (only the ability for the client to access the server on the
specified loader port, so must provide access if running through
firewall).</para>
+
+ <para><emphasis role="bold">Note.</emphasis> Prior to
release 2.2.3, only the
+ parameters in the <classname>InvokerLocator</classname> were used to
configure
+ marshallers and unmarshallers. As of release 2.2.3 the parameters in the
+ configuration map passed to an
<classname>org.jboss.remoting.Client</classname>
+ or <classname>org.jboss.remoting.transport.Connector</classname> will
also
+ be used if the parameter
+
<code>org.jboss.remoting.Remoting.PASS_CONFIG_MAP_TO_MARSHAL_FACTORY</code>
+ (actual value "passConfigMapToMarshalFactory") is set to
"true".</para>
<bridgehead>Compression marshalling</bridgehead>
@@ -6196,6 +6205,13 @@
new "connection identity" semantics described in Chapter
<xref linkend="chapter-connection-failure"/>.</para>
+ <para><emphasis
role="bold">PASS_CONFIG_MAP_TO_MARSHAL_FACTORY</emphasis>
+ (actual value "passConfigMapToMarshalFactory") - if set to
"true", tells clients and servers
+ to take parameters for configuring marshallers and unmarshallers from the
+ configuration map passed to <classname>Client</classname>s and
+ <classname>Connector</classname>s in addition to the parameters in the
+ <classname>InvokerLocator</classname>.</para>
+
<para></para>
<bridgehead>org.jboss.remoting.ServerInvoker</bridgehead>
Show replies by date