[jboss-cvs] jboss-seam/doc/reference/en/modules ...
Gavin King
gavin.king at jboss.com
Wed Dec 13 06:07:05 EST 2006
User: gavin
Date: 06/12/13 06:07:05
Modified: doc/reference/en/modules concepts.xml
Log:
note more efficient impl
Revision Changes Path
1.46 +5 -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.45
retrieving revision 1.46
diff -u -b -r1.45 -r1.46
--- concepts.xml 13 Dec 2006 11:06:20 -0000 1.45
+++ concepts.xml 13 Dec 2006 11:07:05 -0000 1.46
@@ -934,11 +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, <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,
+ by calling <literal>setAttribute()</literal> once in every request, <emphasis>unless the (conversation-scoped)
+ 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
More information about the jboss-cvs-commits
mailing list