User: gropi   
  Date: 01/04/21 17:46:07

  Modified:    src/docs advconfig.xml
  Log:
  added information about implications of "optimized" switch
  in container-invoker-conf.
  Written by Toby Cabot
  
  Revision  Changes    Path
  1.6       +19 -0     manual/src/docs/advconfig.xml
  
  Index: advconfig.xml
  ===================================================================
  RCS file: /cvsroot/jboss/manual/src/docs/advconfig.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- advconfig.xml     2001/04/04 20:37:00     1.5
  +++ advconfig.xml     2001/04/22 00:46:07     1.6
  @@ -437,6 +437,25 @@
                                <listitem>
                                        <para><![CDATA[<container-invoker-conf> 
configuration of the container invoker. 
   ]]></para>
  +<para> There are several elements which can nest within
  +container-invoker-conf, one of which is <![CDATA[<Optimized>]]>.  This
  +controls the behavior of bean method calls within the Java VM in which
  +jboss is running.  If the value of Optimized is "false" then the
  +container will behave per the EJB spec and all objects passed into and
  +out of bean remote methods will be marshalled over RMI regardless of
  +whether the client is running remotely or in the same VM as jboss.</para>
  +
  +<para> If the value of Optimized is "true" then objects passed between
  +bean methods and clients in the jboss java VM will be passed by
  +reference rather than by value.  This is <emphasis>much</emphasis>
  +more efficient (and can result in substantial performance
  +improvements) but can result in unexpected behavior.  For example, if
  +a bean has a member object and returns that object from a get() method
  +then the EJB-specified behavior is to make a copy of that object which
  +is returned over RMI to the caller.  Therefore if the caller modifies
  +the returned object in any way she will modify the copy of the object.
  +If Optimized is "true" then the caller will modify the original object
  +per se, rather than a copy.</para>
                                </listitem>
                                <listitem>
                                        <para><![CDATA[<container-cache-conf> 
configuration of the cache. See below for more details.
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to