Affects Version/s: 1.1.3
Fix Version/s: None
Environment:Windows XP, BEA Weblogic 8.1, JDK 1.4.2, but probably not restricted to this environment.
[A similar issue was already open under MYFACES-218.]
We use ISO-8859-1 as the output character set, not UTF-8.
The effect that we notice is the same as stated in
In this environment it is no longer easy to go over all the returned strings and use some client-side replacement function, because the client-side code is part of the Ajax4JSF project. Also, implementing some un-escaping functionality on the client side makes the client dependent on particulars of the server-side JSF implementation.