title: ViewExpiredException on every navigation after migrating from JSF 1.2 to JSF 2.0
body: <p>I'm attempting to migrate an existing JSF application from JSF 1.2 to JSF 2.0.  I was using MyFaces 1.2.8 and want to use MyFaces 2.0.5.</p>
  
  <p>What I'm experiencing with MyFaces 2.0.5 is that the initially requested page will render properly, but any attempt to navigate to another page will result in a <code>ViewExpiredException</code>. The message is:</p>
  
  <p><strong>No saved view state could be found for the view identifier: /SomePageName.jsf</strong> (where "SomePageName" is the name of the page that I am navigating away from)</p>
  
  <p>If I manually type the Faces-friendly URL of the page I wanted to navigate to, such as <a href="http://localhost:8080/MYAPP/SomeOtherPage.jsf" rel="nofollow">http://localhost:8080/MYAPP/SomeOtherPage.jsf</a> , then the other page will be properly rendered. The application also recognizes that I already have a session and does not try to create a new one.</p>
  
  <p>My application consists exclusively of JSP files, as you would expect from a JSF 1.2 app. My intention is to first get the app working in JSF 2.0 and then rewrite each page as a Facelet one at a time.</p>
  
  <p>Some of my navigation rules look like this:</p>
  
  <pre><code>&lt;navigation-rule&gt;
      &lt;display-name&gt;ManagePorts&lt;/displayName&gt;
      &lt;from-view-id&gt;/ManagePorts.jsp&lt;/from-view-id&gt;
      &lt;navigation-case&gt;
          &lt;from-outcome&gt;REFRESH&lt;/from-outcome&gt;
          &lt;to-view-id&gt;/ManagePorts.jsp&lt;/to-view-id&gt;
      &lt;/navigation-case&gt;
  &lt;/navigation-rule&gt;
  </code></pre>
  
  <p>and some look like this:</p>
  
  <pre><code>&lt;navigation-rule&gt;
      &lt;navigation-case&gt;
          &lt;from-outcome&gt;MANAGE_PORT_LIST&lt;/from-outcome&gt;
          &lt;to-view-id&gt;/ManagePorts.jsp&lt;/to-view-id&gt;
      &lt;/navigation-case&gt;
  &lt;/navigation-rule&gt;
  </code></pre>
  
  <p>(I realize that the REFRESH outcome is not the best way to do things, but that was already in the old 1.2 application and I'm not planning to remove it until I start the migration effort)</p>
  
  <p><strong>Can anyone tell me what I might be doing wrong that would cause the navigation to blow up like this?</strong></p>