[jboss-cvs] jboss-seam/doc/reference/en/modules ...

[Gavin King]

  User: gavin   
  Date: 06/12/13 06:06:20

  Modified:    doc/reference/en/modules  concepts.xml
  Log:
  note more efficient impl
  
  Revision  Changes    Path
  1.45      +7 -5      jboss-seam/doc/reference/en/modules/concepts.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: concepts.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/concepts.xml,v
  retrieving revision 1.44
  retrieving revision 1.45
  diff -u -b -r1.44 -r1.45
  --- concepts.xml	30 Nov 2006 02:15:22 -0000	1.44
  +++ concepts.xml	13 Dec 2006 11:06:20 -0000	1.45
  @@ -934,9 +934,11 @@
   
           <para> 
               For session or conversation scoped entity bean components, Seam automatically forces replication to occur
  -            by calling <literal>setAttribute()</literal> once in every request. This strategy is not efficient, so
  -            session or conversation scope entity beans should be used with care. You can always write a stateful session
  -            bean or JavaBean component to "manage" the entity bean instance. For example, 
  +            by calling <literal>setAttribute()</literal> once in every request, <emphasis>unless the entity is currently 
  +            associated with a Seam-managed persistence context, in which case no replication is needed</emphasis>. This 
  +            strategy is not necessarily efficient, so session or conversation scope entity beans should be used with care. 
  +            You can always write a stateful session bean or JavaBean component to "manage" the entity bean instance. 
  +            For example, 
           </para>
   
           <programlisting><![CDATA[@Stateful
  @@ -956,8 +958,8 @@
   }]]></programlisting>
   
           <para> 
  -            Note that the <literal>EntityHome</literal> class in the Seam Framework provides a great example of this
  -            pattern. 
  +            Note that the <literal>EntityHome</literal> class in the Seam Application Framework provides a great example 
  +            of this pattern. 
           </para>
   
       </sect1>