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.
Environment: - S1S nevada Build e.g. Build 030302 en build - All Platforms I've confirmed this on Sol8, Sol9, and Win2000. - only on ja locale I've never seen this on C locale. To Reproduce: 1. Download atacched "test.zip" and unzip. 2. Start IDE in ja locale. 3. Mount unzipped "test" directory as webmodule. 4. Compile "JSP.jsp" file in new webmodule. Following messages are appeared in Output Window. --- JSP.jsp [-1:-1] Validation error messages from tag library c org.xml.sax.SAXParseException: <.....> "Malformed UTF-8 char -- is an XML encoding declaration missing?" <.....> --- <.....> are declared in japanese, and corresponding english sentences are not clear for me.
Created attachment 9266 [details] Test environment is in this archive.
Additional informations: - about locale If I start IDE in C locale and compile this, error is not occurred. - about Japanese characters If I delete all Japanese characters from jsp file and compile, this, error is not occurred. - about tomcat If I deploy this on Tomcat ("internal" or "extenal") and execute, this error is occurred. But i deploy this on Sun One AS and execute, this error is not occurred. - about taglib If I delete 4th line in JSP file ("<%@ taglib prefix="c" ...") and compile this, error is not occurred. If I delete 4 jar files from "test/WEB-INF/lib" directory and compile, this, error is not occurred. Regards, Hiroshi
Hiroshi, can you please - attach the IDE log - try whether things start to work if you change the IDE Integration Mode (on the Tomcat internal installation node in the Server Registry in the Runtime tab) to Minimum, and then execute the page. I currently can't reproduce this bug, because I can not find a Japanese machine in this building !!! Thanks, Petr
Created attachment 9320 [details] Here is zipped Ide.log when this problem occurrs.
Hello Petr, I've invistigated "latest" nevada build (nevada B_030306). All problems are re-appeared in Latest. And, I tryed to switch internal tomcat to "Minimum", nothing was changed. What kind of informations should I provide you, to solve this?? Hiroshi.
I manage to reproduce the issue. It is exactly as you say Hiroshi. On the standalone Tomcat4.0.6 - the attached example runs without difficulties.
The XmlOutputter class is preparing JSP data together with taglibrary info for Tomcat TagLibraryInfo validation. The combination of tag library info (from the standard.jar) and the JSP written in some national encoding ("euc-jp") caused the incorect passing of the JSP+taglib information to the TagLibraryInfo validator. In case of the "euc-jp" encoding the input stream parameter was created using the : new ByteArrayInputStream(buff.toString().getBytes()); Thus, some characters from the original string were incorrectly converted to the input stream. Suggested fix : http://web.netbeans.org/source/browse/web/jspparser/src/org/netbeans/modules/web/jspparser/XmlOutputter.java.diff?r1=1.5&r2=1.6 Code Reviewer : Marek Fukala
Integrated to NB1.5 I18N comment added. See : http://web.netbeans.org/source/browse/web/jspparser/src/org/netbeans/modules/web/jspparser/XmlOutputter.java.diff?r1=1.5&r2=1.7
Hello Milan, I've verified the fixing on Solaris and Windows in followings. - S1S nevada (Build 030321_1) - S1S trunk (Build 030320) - NetBeans Dev (Build 200303210100) But, "latest Linux's nevada installer" couldn't install correctly. I will verify this immediately, when I succeed to install for Linux environment. Please wait to switch the status "verified" for a while.
Hello Milan, I've verified the fixing on Linux. - S1S nevada (Build 030325) Thank you for your fixing !! Hiroshi
This problem has been fixed for Sun ONE Studio 5 release, and NetBeans 3.5 release. And we don't have this issue in the latest release. However, I received a request from customer to implement this fixing in Sierra patch. Would you give me your any thoughts about possiblities to implement into next Sierra patch? Thank you. Keiichi
Try to fix this according to the diff files. Thanks
Closing as FIXED because in trunk and Tegal/Nevada it is fixed, and a new proactive patch for Sierra is not planned. Keiichi replied that the priority for this bug is low and the customer is not pushing for it. Keiichi, if it turns out that the fix for Sierra is required, reopen the bug and send me an email. Thanks.
I've re-confirmed marketing person about this problem. Since the user can use the latest studio, it's no longer the issue. Thank you. Keiichi
Reopening the issue to change assigned from ftsust to sustaining
Assigning to 'sustaining' user
must fix assigned to
setting back to resolved/fixed with sustaining (not ftsust) as assigned-to
the file was compiled without errors. verified: build 1005