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.
Summary: | NetBeans 4.1 does not support pageEncoding attribute of <%@page %> directive in JSP editor | ||
---|---|---|---|
Product: | javaee | Reporter: | javese <javese> |
Component: | JSP Parser | Assignee: | Petr Pisl <ppisl> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 42638 | ||
Bug Blocks: |
Description
javese
2006-01-04 16:21:24 UTC
We did some fixes in this area. We also improve handling encoding for pages, which are not located under web document base. Where are your pages located? You wrote that this work in NB5.0. If this is true, than the issue should be nmarked as fixed in 5.0. Adding JSE keyword, because this issue is in the Sun Java Studio 8. Thanks very much! The pages are under the sub folders of web application base. Another problem is that in JSP fragment (.jspf) files there is no page encoding directive, so NetBeans would be unable to handle them correctly if they contained characters in different encodings. I suggest that NB should allow the user to specify an charset encoding after opening the document. At present the user may open the properties dialog of the document to check the file encoding but cannot change it. There is missing general approach, how to handle encoding and store outside the file. See issue #42638. We need to convince guys form core to build this A/SPI. ok, marked as fixed in 5.0 I set the version 4.1 and set that this issue depends on #42638 |