Quoting Bryan Lewis <[EMAIL PROTECTED]>: > This has been discussed a few times before. For example,
Yes, I have googled a bit and found some small discussions. But they were not to helpful. > As you say, Tapestry doesn't allow the exception to bubble up to the > user, but it does put a worrisome stack trace in the log. The Tapestry > developers weren't highly motivated to fix this minor annoyance :-) so Well, it is more than an annoyance when you deploy in Tomcat 5.5.15, where the exception reporter gets a null pointer exception from the session.getID(). The user will get a tomcat error report and not the logout page. > I just ignored it for a while, and then worked around it in my custom > Engine. It's not pretty but hey, it's a work-around. Thanks. Regards, Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
