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

[Gavin King]

  User: gavin   
  Date: 07/02/26 19:03:28

  Modified:    doc/reference/en/modules   concepts.xml conversations.xml
  Log:
  updates
  
  Revision  Changes    Path
  1.51      +6 -0      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.50
  retrieving revision 1.51
  diff -u -b -r1.50 -r1.51
  --- concepts.xml	5 Feb 2007 05:51:53 -0000	1.50
  +++ concepts.xml	27 Feb 2007 00:03:28 -0000	1.51
  @@ -692,6 +692,12 @@
           </para>
   
           <para> 
  +            For some components, it can be repetitive to have to specify <literal>@In(create=true)</literal> everywhere
  +            they are used. In such cases, you can annotate the component <literal>@AutoCreate</literal>, and then it
  +            will always be created, whenever needed, even without the explicit use of <literal>create=true</literal>.
  +        </para>
  +
  +        <para> 
               You can even inject the value of an expression: 
           </para>
   
  
  
  
  1.27      +10 -0     jboss-seam/doc/reference/en/modules/conversations.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: conversations.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/conversations.xml,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -b -r1.26 -r1.27
  --- conversations.xml	22 Feb 2007 19:47:34 -0000	1.26
  +++ conversations.xml	27 Feb 2007 00:03:28 -0000	1.27
  @@ -259,6 +259,16 @@
               stuff happening when you backbutton.
           </para>
           
  +        <para>
  +            Usually, if a component exists in a parent conversation of the 
  +            current nested conversation, the nested conversation will use
  +            the same instance. Occasionally, it is useful to have a different
  +            instance in each nested conversation, so that the component 
  +            instance that exists in the parent conversation is invisible to
  +            its child conversations. You can achieve this behavior by 
  +            annotating the component <literal>@PerNestedConversation</literal>.
  +        </para>
  +        
       </section>
       
       <section>