Author: ron.sigal(a)jboss.com
Date: 2009-05-16 20:46:24 -0400 (Sat, 16 May 2009)
New Revision: 5258
Modified:
remoting2/branches/2.x/docs/guide/en/chap5.xml
Log:
JBREM-1102: Added discussion of "passConfigMapToMarshalFactory"
Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap5.xml 2009-05-17 00:39:35 UTC (rev 5257)
+++ remoting2/branches/2.x/docs/guide/en/chap5.xml 2009-05-17 00:46:24 UTC (rev 5258)
@@ -2771,6 +2771,14 @@
specified loader port, so must provide access if running through
firewall).</para>
+ <para><emphasis role="bold">Note.</emphasis> Prior to
release 2.5.2, only the
+ parameters in the <classname>InvokerLocator</classname> were used to
configure
+ marshallers and unmarshallers. As of release 2.5.2 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>
<para>A compression marshaller/unmarshaller is available as well which
@@ -6048,6 +6056,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>
+
</section>
<section>
Show replies by date