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

[Gavin King]

  User: gavin   
  Date: 07/01/30 12:17:59

  Modified:    doc/reference/en/modules   gettingstarted.xml
                        persistence.xml
  Log:
  more talking
  
  Revision  Changes    Path
  1.8       +5 -2      jboss-seam/doc/reference/en/modules/gettingstarted.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: gettingstarted.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/gettingstarted.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -b -r1.7 -r1.8
  --- gettingstarted.xml	30 Jan 2007 16:57:03 -0000	1.7
  +++ gettingstarted.xml	30 Jan 2007 17:17:59 -0000	1.8
  @@ -394,8 +394,11 @@
       
       <para>
         You can even define new deployment profiles for your application.
  -      Just add appropriately named files to your project, and select the
  -      name of the profile using <literal>-Dprofile=myprofile</literal>.
  +      Just add appropriately named files to your project&mdash;for example,
  +      <literal>persistence-staging.xml</literal>, 
  +      <literal>import-staging.sql</literal> and 
  +      <literal>myproject-staging-ds.xml</literal>&mdash;and select the
  +      name of the profile using <literal>-Dprofile=staging</literal>.
       </para>
       
     </section>
  
  
  
  1.3       +18 -0     jboss-seam/doc/reference/en/modules/persistence.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: persistence.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/persistence.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -b -r1.2 -r1.3
  --- persistence.xml	28 Jan 2007 05:56:57 -0000	1.2
  +++ persistence.xml	30 Jan 2007 17:17:59 -0000	1.3
  @@ -124,6 +124,15 @@
               </listitem>
           </itemizedlist>
           
  +        <para>
  +            In the next section, we'll tell you how to set up a conversation-scope persistence
  +            context. But first we need to tell you how to enable Seam transaction management.
  +            Note that you can use conversation-scoped persistence contexts without Seam
  +            transaction management, and there are good reasons to use Seam transaction management
  +            even when you're not using Seam-managed persistence contexts. However, the two
  +            facilities were designed to work together, and work best when used together.
  +        </para>
  +        
           <section>
               <title>Enabling Seam-managed transactions</title>
           
  @@ -187,6 +196,15 @@
               conversation context. You can inject it with <literal>@In</literal>.
           </para>
           
  +        <para>
  +            Seam-managed persistence contexts are extremely efficient in a clustered environment.
  +            Seam is able to perform an optimization that EJB 3.0 specification does not allow 
  +            containers to use for container-managed extended persistence contexts. Seam supports
  +            transparent failover of extended persisence contexts, without the need to replicate
  +            any persistence context state between nodes. (We hope to fix this oversight in the
  +            next revision of the EJB spec.)
  +        </para>
  +        
           <section>
           <title>Using a Seam-managed persistence context with JPA</title>