Description of problem:

Page context doesn't work properly with JSF2 partial state-saving. Conversation id is thus not being restored during restore view. Accessing conversation-scoped component during restore view phase breaks long-running conversation state, as new instances are being created instead of restoring the conversation state. 

Possible workarounds are:

1. Disable partial state saving
<context-param>
   <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
   <param-value>false</param-value>
</context-param>

or, 2. Pass the conversation id explicitly, e.g.

<h:commandButton value="Guess" action="#{numberGuess.guess}">
  <s:conversationId/>
</h:commandButton>

or 

<input type='hidden' name='conversationId' value='#{conversation.id}'/>



Version-Release number of selected component (if applicable):

jboss-seam-2.3.0.Final-redhat-1

How reproducible:

Always

Steps to Reproduce:
1. Enable the org.jboss.seam.test.integration.faces.RestoreViewComponentAccessTest
2. Run integration tests
  
Actual results:
Test fails

Expected results:
Test passes

Additional info:

See the upstream https://issues.jboss.org/browse/JBSEAM-4976 and related issues for more information and applicable workarounds.