You don't have a CACHE param, or the supposedly equivalent "cache" param. MyFaces sees this at startup, and goes with the default, true. This means a cryptographic key is generated at startup and stored in application scope. This is an expensive object, so you want to create it as little as possible. Each request uses this object to store and restore the state. Your application knows it should be encrypting the state, but for some reason it cannot find the key in app scope.
Dennis Byrne >-----Original Message----- >From: Mike Kienenberger [mailto:[EMAIL PROTECTED] >Sent: Tuesday, August 1, 2006 09:28 AM >To: 'MyFaces Development' >Subject: Re: Core 1.1.4 > >On 8/1/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: >> Yes, Mike's problem was w/ trunk. >> >> http://www.nabble.com/org.apache.myfaces.secret.CACHE-t1977021.html >> >> Looking back at the conversations that took place both here and the user >> place, I have to say that at this point it appears as though I blew the >> whistle on the core 1.1.4 release too early. > >I haven't said much because I don't really understand the problem. >One thing that is confusing me is that the issue open appeared to be >regarding a case-sensitivity issue. My experience was that a new >'org.apache.myfaces.secret.CACHE' parameter is now required in my >web.xml file that was previously not required, and it's unclear to me >from the documentation what this does or why it's required. > >Not sure if this helps or not :-) >
