Eclipse freezes with Tomcat using request-character-encoding

[Garret Wilson <ga...@globalmentor.com>]

We have a huge problem with Eclipse trying to simply handle Unicode 
characters in form submissions with Tomcat.

As we discussed in a separate thread, a modern browser will submit 
`application/x-www-form-urlencoded` forms with octects encoded from 
UTF-8 bytes (as it should as per HTML5), but the outdated Java Servlet 4 
specification requires the servlet container to interpret the octects as 
ISO-8859-1 bytes. The Servlet 4 mandated way to work around this is to 
add the following to the `WEB-INF/web.xml` file. (See 
https://stackoverflow.com/a/54098750/421049 if you need to refresh your 
memory.)

<request-character-encoding>UTF-8</request-character-encoding>

Basically if we don't do that, _the page will be broken, the submission 
will not be HTML5 compliant, and content will be corrupted_! That's 
pretty bad, in my opinion.

Unfortunately adding the above line to `WEB-INF/web.xml` seems to 
completely freeze Eclipse and generate a lot of errors. I won't include 
the whole stack trace here, but it stems from:

     org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature 
'request-character-encoding' not found.

I've filed [Eclipse Bug 
543377](https://bugs.eclipse.org/bugs/show_bug.cgi?id=543377), but they 
are ignoring it. If anyone could contact someone at Eclipse and relate 
to them the importance of this, I'd appreciate it.

Garret

P.S. Sometimes it boggles my mind that fundamental pieces of the web 
infrastructure completely break with anything but ASCII—in 2019!


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org