My fix for the flash scope bug involves replacing the old HttpServletRequest object in ActionBeanContexts with a new one that mimics the original for the most part and delegates to a live request object when possible (getRequestDispatcher(), etc.). That's all good.
Replacing the HttpServletResponse is a different story. The response object shouldn't be touched after the request cycle has completed. I could just replace it with null. That would be really easy and generally sufficient. But if somebody were to do something we don't expect, it would be hard for them to debug the NullPointerException that would occur. So instead I have created an HttpServletResponseInvocationHandler and replace the response with a dynamic proxy instance. So the response won't be null, but any method call on the response object results in an IllegalStateException that says exactly what went wrong. Does anybody know of a reason not to do this? -Ben ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
