No, just JSF phase listener for authentication. Nothing special. If you
referring to the error in server log, then it shows only in 1.2.x
version of trinidad.
Looking with Firefox live headers bellow mentioned characters are
submitted as "%C5%A1%C4%91%C5%BE%C4%87%C4%8D" in both versions of
trinidad. So it's not problem with browser encoding.
Luka Surija
+385 1 61 99 140
+385 98 434 061
[email protected]
I.Y. tim d.o.o.
Vrbik 3, HR-10000 Zagreb
www.iytim.hr
[email protected]
Matthias Wessendorf wrote:
Are you using some custom filter, that accesses the request map ?
-Matthias
On Tue, Mar 17, 2009 at 5:57 PM, Luka Surija <[email protected]> wrote:
Hi,
I'm stuck with trinidad version 1.0.x. and I can't use any 1.2.x version
because many non us characters are broken. The problem is not in character
displaying this characters, but in submitting.
For example "šđžćč" is correctly displayed in tr:inputText, but after
submitting the same value, it is displayed as "Å¡Ä‘Å¾Ä‡Ä ". This problem is
not only with croatian characters, but also with German umlauts and probably
other non us characters.
I've also noticed that with 1.2.x version of trinidad this error in server
log:
"PWC4011: Unable to set request character encoding to UTF-8 from context
/YP, because request parameters have already been read, or
ServletRequest.getReader() has already been called"
Glassfish 9.1
Trinidad 1.2.11
Facelets 1.1.13
Majorra 1.2_04-b18-p03
--
Luka Surija
+385 1 61 99 140
+385 98 434 061
[email protected]
I.Y. tim d.o.o.
Vrbik 3, HR-10000 Zagreb
www.iytim.hr
[email protected]
