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

[Shane Bryzak]

  User: sbryzak2
  Date: 07/04/13 19:49:38

  Modified:    doc/reference/en/modules  remoting.xml
  Log:
  clarify setting the conversation id
  
  Revision  Changes    Path
  1.22      +12 -0     jboss-seam/doc/reference/en/modules/remoting.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: remoting.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/remoting.xml,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -b -r1.21 -r1.22
  --- remoting.xml	17 Feb 2007 09:33:05 -0000	1.21
  +++ remoting.xml	13 Apr 2007 23:49:38 -0000	1.22
  @@ -346,6 +346,18 @@
         first valid conversation ID that is returned by any remoting call. If you are working with multiple conversations
         within your page, then you may need to explicitly set the conversation ID before each call. If you are working
         with just a single conversation, then you don't need to do anything special. </para>
  +      
  +    <sect2>
  +      <title>Remote calls within the current conversation scope</title>
  +      
  +      <para> In some circumstances it may be required to make a remote call within the scope of the
  +        current view's conversation.  To do this, you must explicitly set the conversation ID to that
  +        of the view before making the remote call.  This small snippet of JavaScript will set the
  +        conversation ID that is used for remoting calls to the current view's conversation ID: </para>
  +        
  +      <programlisting><![CDATA[  Seam.Remoting.getContext().setConversationId( #{conversationId} );
  +      ]]></programlisting>
  +    </sect2>
     </sect1>
   
     <sect1>