Author: gpetracek Date: Sun Jan 5 22:22:36 2014 New Revision: 1555641 URL: http://svn.apache.org/r1555641 Log: updated content
Modified: deltaspike/site/trunk/content/jsf.mdtext Modified: deltaspike/site/trunk/content/jsf.mdtext URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/jsf.mdtext?rev=1555641&r1=1555640&r2=1555641&view=diff ============================================================================== --- deltaspike/site/trunk/content/jsf.mdtext (original) +++ deltaspike/site/trunk/content/jsf.mdtext Sun Jan 5 22:22:36 2014 @@ -742,10 +742,10 @@ The same is supported for folders via `F Available with all versions after 0.5. -DeltaSpike conversations are based on the window-scope. Therefore, don't forget to add the `ds:windowId` (`xmlns:ds="http://deltaspike.apache.org/jsf"`) component in case of ClientWindowConfig#CLIENTWINDOW to your page(/template) and ensure that the window-handling works properly (otherwise conversations won't work correctly). +DeltaSpike conversations are based on the window-scope. Therefore, don't forget to add the `ds:windowId` (`xmlns:ds="http://deltaspike.apache.org/jsf"`) component in case of `ClientWindowConfig#CLIENTWINDOW` to your page(/template) and ensure that the window-handling works properly (otherwise conversations won't work correctly). The base principle is similar to CODI-Conversations. CODI users just have to ensure that they have to add `ds:windowId` and the names are slightly different. -First of all it's important to mention that DeltaSpike starts (grouped) conversations automatically as soon as you access conversation scoped beans. Furthermore, the invocation of GroupedConversation#close leads to an immediate termination of the conversation. +First of all it's important to mention that DeltaSpike starts (grouped) conversations automatically as soon as you access conversation scoped beans. Furthermore, the invocation of `GroupedConversation#close` leads to an immediate termination of the conversation. :::java @GroupedConversationScoped