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.
The nodes under Options->IDE Configuration->Settings->File Types in the Forte 4.0 ea builds are expandable, but every time it is expanded, the subnode says ... parsing error.
If you mount NetBeans system catalog (Runtime->XML Entity Catalogs->NetBeans Catalog) than xml document is parsed ok. Regarding to it is expandable I am not sure about it. It is real XML document so XML module catch it. In dev builds those File Types documents are not expandable and XML module did not change anything for it. It is Core issue. From my side it is not XML module bug. I think core should guarantee it will not be expandable.
Someone should fix this even if it's not xml
Reassigning to core owner
Agreed. The same behaviour is in nb 3.4. They shouldn't be expandable. Also see issue #22628. IMHO this one is a duplicate.
I guess this could be considered a dupe of #22628. For myself, I don't think this is a bug. There are some XML files. As with all other XML files, you can expand them to see a parse. As with all other XML files, you need to make sure that you have mounted any needed entity catalogs first. Maybe the files can be made non-expandable if someone cares, but I don't see it as a defect that they are expandable. So marking a UI enhancement for now. It would be nice if the XML module displayed a more specific message than "parse error", e.g. "entity not found", but that is true of XML files generally.
Sorry, but if the out of the box installation of the IDE has an error when expanding a node, I think this is a bug. I don't care whether it's expandable or not. Either it should be made not expandable, or the entity should be found automatically by the thing that does the xml layer parsing. There should be *no* error, not a friendlier one =).
I think issue #22628 describes similar problem. I think all XML documents under system should be caught as "XML Configuration Files".
All right, can treat as UI defect then. In that case I agree with Libor, issue #22628 if fixed as currently suggested - core recognizes all XML files on system file system - would provide a solution for this as well. Or rather, there would still be an expand handle I think, since org.openide.loaders.XMLDataObject cannot use Children.LEAF and still be able to switch to different children when new processors are installed, but if expanded there would be no children, so it wouldn't look so bad. Some day maybe entity resolvers could be structurally edited by users anyway - not sure if this would be useful to anyone, but it is a possibility. *** This issue has been marked as a duplicate of 22628 ***
Resolved for 3.4.x or earlier, no new info since then -> verified.
Resolved for 3.4.x or earlier, no new info since then -> closing.