I put a <jsp:scriptlet> in my login page with a System.out.println... well, it is being processed! But in the result page there is no trace of it. The login page is completely discarded, even if the browser seems to refresh the page, the same content is redisplayed (without any JSF processing).
Big, big problem.. maybe XmlHttpRequest has better support for container managed security, but in the meantime? I'm opening a JIRA for this issue. Cosma 2006/6/23, Cosma Colanicchia <[EMAIL PROTECTED]>:
Hi, I need paginated <af:table>s in a webapp configured to use form based authentication. Normally, on session time outs, the container saves all the request information in session, brings me on the login page and then "replay" the original request. This usually works fine with STATE_SAVING_METHOD "client" and CLIENT_STATE_METHOD "all" and a wise usage of session-scoped managed beans. But if there was an <af:table> on the page when the session timed out, and I try to navigate on another page, something is going wrong: the same view is redisplayed, no login, no new table page. I suspected the problem was related to PPR, so I tried to set partialTrigger="false" on my <afh:body> and on <af:table>, but this didn't solved anything. If I disable the authentication in my web.xml the problems doesn't happen. The container on which I'm testing is the OC4J embedded in JDeveloper 10.1.3. Please can someone helps me with this? I'm spending much work to make the webapp session timeout tollerant, it is a strong requirement for our environment, and this is a real show stopper. Thanks in advance Cosma
