Hi, We are getting this error when the application runs behind a proxy. The error disappears when excluding the server from the proxy (via the setting in the browser).
Luka Surija wrote: > > From time to time (random on deployment or app server restart), I have > the same problem but I'm using RI jsf 1.2, trinidad 1.0.7 and facelets > 1.1.13. So it looks like some kind of problem in facelets?? And yes, the > problem appears to be related with params in url. For example: > index.xhtml?someparam=somevalue. Displaying index.xhtml without params, > works fine, but trinidad also uses params for Dialog framework, so there > is often point of breakdown. > > Any clue? > > Luka > > lmk wrote: >> Hii, >> >> I try to add com.sun.faces.enableRestoreView11Compatibility=true, without >> success, >> is this a myfaces bug, a JSF spec problem or faceletes issue...I dont >> now.. >> I dont want to override the FaceletsViewHandlers..it exist any clean >> solution ..? >> >> thanks.. >> >> >> >> lmk wrote: >> >>> hello, >>> >>> I get a strange problem after migration from myfaces 1.1.5 to 1.2.2.. >>> I send an ajaw request after session timeout, >>> I get error: >>> >>> javax.faces.application.ViewExpiredException: /result.jsfThe expected >>> view >>> was not returned for the view identifier: /result.jsf >>> >>> thanks for help >>> >>> >>> >>> >>> >>> >> >> > > > -- View this message in context: http://www.nabble.com/-myfaces-1.2.2--session-timeout-issue-tp16627912p16833571.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
