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: | AU(Crimson) cannot parse Unicode entity includes | ||
---|---|---|---|
Product: | platform | Reporter: | Jesse Glick <jglick> |
Component: | Autoupdate | Assignee: | Jiri Rechtacek <jrechtacek> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | mihmax, rbalada, rnovak |
Priority: | P4 | Keywords: | I18N |
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 22948, 33098 | ||
Attachments: | Stack trace |
Description
Jesse Glick
2003-04-21 16:20:08 UTC
Created attachment 10051 [details]
Stack trace
Yes it looks like a bug in Crimson. Seems like the only difference between file:// and http:// connection is that the first one retuns contentType unknown the second one returns text/xml. Making the server to return proper encoding could help but is probably impossible to achieve on NetBeans server. I've tested Jesses second proposal for not using !ENTITY in the XML file and it works. I'll try to organize this for the NetBeans server. I don't put some hacks into the Au client to obtain xerces instead of crimson. Adding Robert Novak on CC. The NetBeans AU center should avoid using XML entities. This will workaround the bug in the Crimson parser. However the issue with crimson should be solved somehow. Not sure how. I think Ruda actually handles the daily alpha build. Funny about the Content-Type - text/xml is the *correct* type for the *.ent file. Hmm. Maybe if the Crimson problem can be reproduced in a standalone app, file a bug on xml.apache.org. *** Issue 33264 has been marked as a duplicate of this issue. *** I suggest this issue be P2, bacause it blocks me connecting to NetBeans Alpha AU server Need not be P2. This bug has already been worked around, as Petr mentioned, and is lower priority. Issue #33264 is unrelated. What's the issue # of a workaround? Maxym, I guess, that the workaround is to not use reference to external !ENTITY within the .xml file. *** Issue 7946 has been marked as a duplicate of this issue. *** reassigne to Jirka - new owner of autoupdate Seems as WONTFIX. Crimson is not used in AU anymore. Reopen if I'm wrong. Oops, I'm wrong, openide.xml/XMLUtil.parse() returns crimson still. I reopen it. It's this bug still anywhere visible? It is presumably still visible if you have an UC XML file using entity includes. Currently netbeans.org does not but someone else may well try it. Probably not high priority. I guess this won't be fixed for NB4.0 , please evaluate again. I feel it's problem won't be tracked no longer. No other bugs don't depend on this. Closed as WONTFIX. x I feel it's problem won't be tracked no longer. No other bugs don't depend on this. Closed as WONTFIX. |