Mark,

On 12/6/22 03:28, Mark Thomas wrote:
On 05/12/2022 20:32, Christopher Schultz wrote:

<snip/>

4. Patch the server to provide #3 without having to include a Filter in the application deployment.

5. Extend the migration tool so you can add file extension / file type mappings in addition to the built-in ones. Or maybe even override the built-in ones. This is a lot more work than #4.

I'm kind of interested in idea #4, and wanted to ask for feedback.

I think #4 could be a nest solution applicable to multiple users.

If placed at the end of the current getAttribute() code it would have a minimal performance impact.

We should log (debug level?, separate logger like NioEndpoint.handshake?) when this happens.

I can't be the only one in this situation where the Tomcat Migration Tool is great but doesn't cover some use-cases and therefore upgrades are risky and/or problematic.

I'm sure. I'm expecting a bunch of issues to start showing up as folks start migrating.

I think we as a community should be encouraging users to start upgrading to get over the "Jakarta Hurdle" and I think that this could be another small tool to help motivate that migration.

WDYT?

+1.

Cool. Based upon that feedback, I'll start working on a Filter as a PoC. It can easily be converted to a Valve or just added to Request.getAttribute.

Time for a good re-reading of the servlet spec documentation ;)

-chris

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to