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 <[EMAIL PROTECTED]>: > > > > > 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=a5 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 login > 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 this > 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äftsführer: > 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
