search

me0wster / javamelody

Automatically exported from code.google.com/p/javamelody
0 stars 0 forks source link

javamelody affects to non-ISO encoding webpages #239

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Under Tomcat 5.5, using javamelody is affecting to the enconding rendered in 
our webpages, when using a spanish encoding special characters are not 
displayed correctly. Disabling javamelody solves the issue. I haven't tested it 
under Tomcat 6 or 7 (that's what I plan to do).

JDK 1.6 under Centos 5.2.

Miguel

Original issue reported on code.google.com by miguel_3...@yahoo.es on 24 Jul 2012 at 9:47

GoogleCodeExporter commented 9 years ago 
Do you have an example webapp to reproduce the problem?
Thanks.

Original comment by evernat@free.fr on 25 Jul 2012 at 5:05

GoogleCodeExporter commented 9 years ago 
herewith you have an example of a struts webapp.

Miguel

Original comment by miguel_3...@yahoo.es on 29 Jul 2012 at 9:23

Attachments:

GoogleCodeExporter commented 9 years ago 
Did you have the chance to test it?

Miguel

Original comment by miguel_3...@yahoo.es on 7 Aug 2012 at 9:57

GoogleCodeExporter commented 9 years ago 
not yet, I plan to look at it in a few days

Original comment by evernat@free.fr on 7 Aug 2012 at 11:32

GoogleCodeExporter commented 9 years ago 
Hi,
1. At first, I did not have seen that it was with Tomcat 5.5.
Do you have tested with Tomcat 6 or 7?

2. Then, there is a lot of unknown jar files and sources/classes in this 
webapp. In particular, I do not know about anything about the Xzaro.jar file in 
this webapp.
Do you have a simpler example webapp to reproduce the problem, with less jar 
files and classes?

Original comment by evernat@free.fr on 10 Aug 2012 at 9:27

GoogleCodeExporter commented 9 years ago 
I haven't tested it with Tomcat 6, but it is not working under Tomcat 7 either. 
I'll try to get a simpler webapp from our developer.

Original comment by miguel_3...@yahoo.es on 11 Aug 2012 at 10:04

GoogleCodeExporter commented 9 years ago 
Our developer trimmed some jars and classes. herewith you have a newer zip 
file. We can't take out more classes, otherwise we can't reproduce the issue.

Regards

Miguel

Original comment by miguel_3...@yahoo.es on 19 Aug 2012 at 2:52

Attachments:

GoogleCodeExporter commented 9 years ago 
There is still the Xzaro.jar file (and some others). I do not know anything 
about this jar file.
So for security reasons, I can't test this webapp.

If you can't reproduce the issue when you take out more classes/jar files, then 
it make me thinks that the issue is probably in your application or in one of 
your paleolithic libraries (for example, struts 1.1 or hibernate 2.1.7). 
Moreover, there never was other javamelody users seeing an issue like this one.

By the way, you don't need to put the servlet.jar file in the WEB-INF/lib/ 
directory of your webapp.

Original comment by evernat@free.fr on 25 Aug 2012 at 2:42