Re: [undertow-dev] Deadlock in JSP page on Wilflfy 8.0 Alpha 4 with umlauts

Ok, fixed for real this time. The form parser was defaulting to UTF-8 when no charset was present in the request. Stuart ----- Original Message ----- > From: "Stuart Douglas" <sdouglas(a)redhat.com&gt; > To: "Wolfgang Knauf" <wolfgang.knauf(a)gmx.de&gt; > Cc: undertow-dev(a)lists.jboss.org > Sent: Thursday, 29 August, 2013 2:39:35 PM > Subject: Re: [undertow-dev] Deadlock in JSP page on Wilflfy 8.0 Alpha 4 with umlauts > > > > ----- Original Message ----- >> From: "Wolfgang Knauf" <wolfgang.knauf(a)gmx.de&gt; >> To: "Stuart Douglas" <sdouglas(a)redhat.com&gt; >> Cc: undertow-dev(a)lists.jboss.org >> Sent: Thursday, 29 August, 2013 2:30:20 PM >> Subject: Aw: Re: [undertow-dev] Deadlock in JSP page on Wilflfy 8.0 Alpha 4 >> with umlauts >> >> Hi Stuart, >> thanks for the fast fix! The question mark is probably some kind of >> standard >> for non displayable strings ;-). Maybe also a log message, to trace down >> the >> error better? >> Any chance for me to test this against WildFly 8 Alpha 4 (without building >> it >> myself)? > > Unfortunatly not yet. Once I release Undertow (probably next week) it will be > possible to get a nightly build. > >> I assume that on my JSP page which handles the request, I have to do >> something like this: >> request.setCharacterEncoding ("ISO-8859-1"); > > This is the default character set. Hmm, I need to investigate what is going > on here, this is just using the standard charset encoder for ISO-8859-1, so > I am not sure why it is reporting those characters as unmappable. > > Stuart > >> This should hopefully write the correct characters to the database. I will >> do >> more testing this evening. >> On previous JBoss versions, my sample worked without those modifications. >> Did >> the Undertow migration include some change to character encoding handling? > > Hmm, I will need to investigate this, and see how this was handled in > previous versions. >