On 1/4/07, Matt Finholt <[EMAIL PROTECTED]> wrote:
Hi Matt, Thanks for your advice! It was very helpful in exposing another layer of the issue! As it turns out, the error isn't related to the initial page request at all. Instead, the error is thrown when a css file is requested that doesn't exist within the file system. On a hunch, I temporarily removed the "struts-cleanup" filter mapping and the error went away.
Weird. If the CSS file exists (there's no 404), does this error still happen. Matt
Hopefully this will be a non-issue by the time Struts 2 goes final. Thanks again, Matt Can you try deleting parts of your JSP page until you see the real error? You might try removing error.jsp from web.xml to see if you can get a better stack trace from the server. Either that, or try putting a debugger in the getSession() or getRequest() calls in BaseAction - it looks like it might be happening there. Matt -- View this message in context: http://www.nabble.com/AppFuse-1.9.3---WebWork-2.2.4-migrate-to-Struts2-tf2915402s2369.html#a8165393 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
