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.
A space in a directory name, e.g. "Documents and Settings", causes catalog looks to fail. If you place the same catalog under a directory structure without spaces, it works. The file URL listed under 'XML Entity Catalogs' in the 'Runtime' tab does not have the spaces escaped properly.
Yes Alex is right. It still does not work in development build #200502170805 of NetBeans 4.1. If the catalog with space in path is mounted, its subnodes have "View" menu disabled.
I cannot reproduce on my linux. It's not probably related just to spaces. I suspect it's triggered by wrong URL normalization (":" and " ") done in 3rd party catalog impl code. What nane does have your catalog node? I get "Resolver at file:/home/pk97937/bugs/is53/x710/a space in path/newXMLCatalog.xml" that is probably wrong as it lacks proper space escaping. Hey, I can reproduce now. Catalog location does not matter. It's content matters. Here bundled com.sun.resolver.tools.CatalogResolver implementation relies with null systemID if the systemID(URI) contains spaces. It's easily observable just look at catalog entry properties. If System ID contains null you suffer from the provider bug. It's defacto duplicate of issue 27930 that fixes this.
Yes, you are right. The value of System ID is null. I would also agree to resolve this issue as duplicate of the #27930. Do you really plan to fix this one in 4.1 ?
As the submitter of this who discovered this when I have 20 students in masters program at UC Berkeley not able to use their catalogs, I'd say it is really important! They were totally confused. They typically put the files in "Documents and Settings" on windows and it just didn't work. It took a bit of sleuthing on my part as I hate spaces in directory names so I had never run into this problem. Basically, on windows it is very normal to have spaces in file names and your average user will not understand why their catalog fails to work.
Now, after the resolver library upgrage, it works for: uri="a space/my.dtd" uri="a%20space/my.dtd" but it does not work for: uri="a+space/my.dtd" (proper systemID is returned but parser is not able to access it, probably known bug in URL.openStream() implementation). I'm going to try to write workaround to cover all space syntaxes.
FIXED, code readability and maintainability decreased but all 3 syntaxes supported. Checking in src/org/netbeans/modules/xml/catalog/CatalogEntityResolver.java; /cvs/xml/catalog/src/org/netbeans/modules/xml/catalog/CatalogEntityResolver.java,v <-- CatalogEntityResolver.java new revision: 1.15; previous revision: 1.14 done Checking in src/org/netbeans/modules/xml/catalog/CatalogEntry.java; /cvs/xml/catalog/src/org/netbeans/modules/xml/catalog/CatalogEntry.java,v <-- CatalogEntry.java new revision: 1.4; previous revision: 1.3
Fix Verified: spaces replaced w/ %20 and catalogs do not fail. Product Version: NetBeans IDE Dev (Build 200802151203) Java: 1.5.0_13; Java HotSpot(TM) Client VM 1.5.0_13-119 System: Mac OS X version 10.5.2 running on i386; MacRoman; en_US (nb)