This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
If a JSP in standard syntax has page directives with pageEncoding and contentType attributes, then loading the file also sets the charset attribute after the contentType. This can be verified by using the current JSP template, which has contentType="text/html" and pageEncoding="UTF-8". The contentType comes out as "text/html;charset=UTF-8". Setting the charset attribute is not the right thing to do in this case. Unless the user sets the charset some other way, it will default to the pageEncoding anyway. If they do want to set it elsewhere (for example in a servlet); then setting it again is either ineffectual (because it is too late) or it, if it's not too late, then it potentially has the effect of overwriting behaviour that the user has coded elsewhere.
I recommend that this be fixed for 3.6
It seams like bug in jsp parser. If there are defined different encoding in the charset and pageEncoding, then the right encoding is the pageEncoding, but the parser returns encoding in charset. If there is defined encoding in the deployment descriptor for the jsp page, then the parser returns the right encoding from DD.
I filled new bug against tomcat: http://www.netbeans.org/issues/show_bug.cgi?id=40791
In the tamplate is not inserted the charset now.
v