void function ( ) { popContextOnNextPauseCounter ++ ; }
increment the number of conversation context that must be popped from the stack by the conversation manager when it pauses the current conversation . why do n't we pop directly the context here ? when an action is triggered from within a datatable , the jsf runtime executes some el after our action . by doing so it requests a conversation scoped bean that belongs to the current context . if this context is popped too soon , the bean is recreated ! concode_field_sep Stack<ConversationContext<?>> contextes concode_elem_sep String CONVERSATION_COUNTER_KEY concode_elem_sep int conversationContextIdCounter concode_elem_sep Logger log concode_elem_sep int popContextOnNextPauseCounter concode_elem_sep ConversationContext<?> nextContext concode_elem_sep Map<String,Object> beans concode_elem_sep long serialVersionUID concode_elem_sep String id concode_field_sep String getCid concode_elem_sep String getLabel concode_elem_sep void handleOutOfSynchContext concode_elem_sep T getCurrentContext concode_elem_sep void setVar concode_elem_sep void popContextesIfNeeded concode_elem_sep Stack<ConversationContext<?>> getConversationContextes concode_elem_sep String getId concode_elem_sep int getPopContextOnNextPauseCounter concode_elem_sep int getConversationContextesCount concode_elem_sep String nextUrl concode_elem_sep void addBean concode_elem_sep void setNextContextSub concode_elem_sep String getUrl concode_elem_sep String getViewUri concode_elem_sep ConversationContext<?> nextContext concode_elem_sep T nextContext concode_elem_sep Object getVar concode_elem_sep T getVar concode_elem_sep Conversation newConversation concode_elem_sep Conversation newConversation concode_elem_sep void pushNextContextIfNeeded concode_elem_sep Object getBean concode_elem_sep void setNextContextReadOnly concode_elem_sep void setNextContext concode_elem_sep String nextView concode_elem_sep void setNextContextSubReadOnly