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 I want to edit an XML document in UTF-8 encoding with UTF-8 marker byte at the beginning of the file (generated with "Save As" UTF-8 format in Windows 2000 Notepad), then NetBeans cannot parse the document. If I remove the leading UTF-8 marker byte, then it works. Using JDK 1.4.1 RC. Attaching an example XML.
Created attachment 7273 [details] An example unparsable UTF-8 XML.
It is bug in JDK you can vote for it. http://developer.java.sun.com/developer/bugParade/bugs/4508058.html
OK, I voted for it, but I don't think Sun will change this in the near future. But this problem renders the XML features of NetBeans useless (at least for us). A workaround should be implemented in NetBeans. BTW, Xerces can load such files without problems.
Uh, XML modules use Xerces (2.0.0 beta 4). Have you tried alternative JDK such as IBMs? Does it work with it? Text editing works, but I assume that the BOM is destroyed on save (is it OK?).
We are loading this XML without problems into our application with Xerces 2.0.1. Text editing works, that's right and the marker is not destroyed on save (if I don't press DEL at the beginning of the file). But we need the tree editor and the schema validation to work.
Forget to answer the JDK question: We are only using Sun's JDK.
Looks it is fixed in latest Xerces releases, module's Xerces should be updated.
Later.
OK, but do not use 2.0.2 or 2.1.0, use 2.0.1. The newer ones have severe problems with spaces in directory paths. BTW: Can I switch NB 3.4 to Xerces 2.0.1 myself?
NetBeans 3.4 uses Xerces 2.0.1, except for parsing XML file into internal model (Xerces 2.0.0 beta 4 used). You can port it we use XNI based builder. Unfortunately XNI have changed (and next changes are announced), therefore you need to map old XNI calls to new XNI calls. Class org.netbeans.tax.io.XNIBuilder.
Thomas have you reported space in path bug at Apache's. No such is reported or it is already fixed (see URL field).
I just filed the bug (discovered yesterday), but your query does not find it. Use: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12257
About porting to Xerces 2.0.1: Sorry, I am not familiar with XNI and don't have the time at the moment.
More details in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10633.
URL update, Xerces contains 78 open bugs.
5,5 years later the bug still exists... Tested with JDK 1.6.
*** This issue has been marked as a duplicate of 83321 ***