Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 20327 invoked from network); 8 Feb 2008 11:21:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Feb 2008 11:21:09 -0000 Received: (qmail 41911 invoked by uid 500); 8 Feb 2008 11:20:49 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 41878 invoked by uid 500); 8 Feb 2008 11:20:49 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 41844 invoked by uid 99); 8 Feb 2008 11:20:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2008 03:20:49 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mwessendorf@gmail.com designates 209.85.146.178 as permitted sender) Received: from [209.85.146.178] (HELO wa-out-1112.google.com) (209.85.146.178) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2008 11:20:16 +0000 Received: by wa-out-1112.google.com with SMTP id l24so388863waf.22 for ; Fri, 08 Feb 2008 03:20:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=Z2AgY1CpubRtc1fJGuU3sScoa7iRYGwxPRi3QvdpHJ8=; b=sevoi+cAwOB5QOLn37UqX/dLTYdKoCk/l4aKCY3aP53t39pEwcpbgB8mg3FndP4dmwe09E7YSlAO/VD9qCFtmsF/bWvQYUrIPaQfAe6Qc+hrVlHaVk4ECV0ZqwUa3avs7D2WuChmXS+isSESJY/DDIq3BF1bSmewj1vSYFBgg+A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=L+T2mQHss9oy+Pn6F87gS4n1bxC8t+ZJbSmrhBJIPG5GsQyk44WkoCGU8vDbWdNioJq5okRn6VxSi2EktC5y7Dq73y0XEZDjG1YckZqY8/xfwe4KG4L4lW5jTUfkWI1as23cGzru3/qTQX7nBrM6wPaO/HcvLJNPL1ZSLIJpcD4= Received: by 10.114.14.1 with SMTP id 1mr4716386wan.9.1202469624036; Fri, 08 Feb 2008 03:20:24 -0800 (PST) Received: by 10.115.54.11 with HTTP; Fri, 8 Feb 2008 03:20:24 -0800 (PST) Message-ID: <71235db40802080320k45ff0d27g4a7c3c827c1d0d4f@mail.gmail.com> Date: Fri, 8 Feb 2008 12:20:24 +0100 From: "Matthias Wessendorf" Sender: mwessendorf@gmail.com To: "MyFaces Discussion" Subject: Re: [Trinidad] problem with PPR behaviour after timeout In-Reply-To: <71235db40802080309n6292a011l63a49a973f5a5d41@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <71235db40802080309n6292a011l63a49a973f5a5d41@mail.gmail.com> X-Google-Sender-Auth: a04200580276da49 X-Virus-Checked: Checked by ClamAV on apache.org like public class SessionListener implements Filter { /** * session timeout page */ private final String SESSION_TIMEOUT_PAGE =3D "sessionTimeout.jsp"; /** * do filter method * @param servlet request * @param servlet response * @param filter chain */ public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws ServletException, IOException { // check session availability if(null =3D=3D ((HttpServletRequest) request).getSession(false)) { // dispatch to session timeout page, due to the session is not available request.getRequestDispatcher(SESSION_TIMEOUT_PAGE).forward(request,= response); } else { chain.doFilter(request,response); } } public void destroy() {/* nothing to do */} public void init(FilterConfig arg0) throws ServletException {/* nothing to do */} } On Feb 8, 2008 12:09 PM, Matthias Wessendorf wrote: > Hi, > > you mean like you have a page, with some PPR triggers (like button) > and after 40 minutes you click a button to finally see the JS errors ? > > Have you tried to implement a session listener to redirect (to > start/login page) after timeout? > > -M > > 2008/2/8 : > > > > > > > > > > > Hi, > > > > Generally I wonder what the concept/design of PPR is when a timeout has > > occurred > > because the current default PPR behaviour does not fit in this scenario= and > > one gets > > an error, actually two JS errors > > > > "TypeError: a5 has no properties message=3Da5 has no properties" > > "Invalid PPR response. The response-headers were:\nServer: > > Apache-Coyote/1.1\nX-Powered-By: Servlet 2.4..."]" > > > > The reason is that in such a situation the server sends a complete logi= n > > page contrary to the specific > > PPR response that is expected. > > > > How can you deal with PPR in such a situation? Is there any built-in > > design, if so which, if not, > > is there a regular Trinidad-based approach/workaround to dealing with t= his > > scenario? > > > > Many thanks,Wolfgang. > > > > PTA Programmier-Technische Arbeiten GmbH > > Seckenheimer Str. 65-67, 68165 Mannheim > > Amtsgericht Mannheim, HRB 1139 > > USt-IdNr.: DE 143 839 368 > > Gesch=E4ftsf=FChrer: > > Dipl.-Ing. Peter Fischer > > Dr. Harald W. Busch > > Dipl.-Kfm. Knut Fischer > > > > ********************************************************************** > > http://www.pta.de > > Mit 1547 Erfahrungsberichten aus 39 Jahren erfolgreicher Projektarbeit! > > ********************************************************************** > > > > > > > > -- > Matthias Wessendorf > > further stuff: > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > mail: matzew-at-apache-dot-org > --=20 Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org