ruthst00 commented on PR #16516: URL: https://github.com/apache/grails-core/pull/16516#issuecomment-6130952360
@jdaugherty, @jamesfredley, with guidance from the Reporter of the issue (@ivaylodimov-taulia), I was able to reproduce the exception with a simple [Grails 8 app](https://github.com/ruthst00/15819-response-renderer-overloads) containing a Spring `RequestContextFilter` that runs after `GrailsWebRequestFilter`. With this new information I made the following updates with commit https://github.com/apache/grails-core/pull/16516/changes/8eacc339d6256223ff533ebeed85296f1c2a6ced: ### Changes - The dispatcher now reuses the active `GrailsWebRequest` when a later `RequestContextFilter` replaces the thread binding. - Newly created instances are also published as the request attribute, keeping renderer and URL-mapping lookups consistent. - Added regression coverage for uncommitted template rendering with both null and Map action returns. - Added lifecycle coverage for completed requests, async/error redispatch, and nested include/forward restoration. - Updated the rendering documentation. Existing branch fixes were retained. ### Verification - Confirmed both late-filter regression cases fail with the original dispatcher implementation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
