Author: manaRH
Date: 2012-08-08 14:58:22 -0400 (Wed, 08 Aug 2012)
New Revision: 15023
Modified:
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Concepts.xml
Log:
JBSEAM-5006 documentation note about change for @Synchronized and SFSB
Modified:
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Concepts.xml
===================================================================
---
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Concepts.xml
2012-08-08 18:27:29 UTC (rev 15022)
+++
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Concepts.xml
2012-08-08 18:58:22 UTC (rev 15023)
@@ -278,6 +278,12 @@
<emphasis>extremely</emphasis> expensive. However, you can
force a serialized threading model on any
session bean or JavaBean component by adding the
<literal>@Synchronized</literal> annotation.
</para>
+ <note>
+ <para>Seam 2.3 removed the serialization of Stateful
+ session beans by Seam synchronization interceptor
+ because stateful session beans are serialized by EJB 3.1
+ container by default .</para>
+ </note>
<para>
This concurrency model means that AJAX clients can safely use
volatile session and conversational
state, without the need for any special work on the part of
the developer.
_______________________________________________
seam-commits mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-commits
