You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/03/02 21:39:32 UTC
DO NOT REPLY [Bug 16335] -
Setting Jasper logging level to DEBUG causes request.setCharacterencoding() to be ignored
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16335>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16335
Setting Jasper logging level to DEBUG causes request.setCharacterencoding() to be ignored
markt@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From markt@apache.org 2004-03-02 20:39 -------
I appreciate the problem you describe and agree with the principle that
turning on debug shouldn't alter behaviour.
The choice here is between including the parameters in the debug output and
causing the problem you describe or not including them and depriving
developer of a lot of useful information.
On balance I think we should keep the existing behaviour. There are a number
of alternative approaches you can take to set the parameter encoding that may
help you by setting the encoding before you reach the debug statement. Have a
look at bug 22666 for a description of these options (and other character
encoding issues)
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org