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.
This is desirable mainly for adding DTD references in order to provide xml files with code completion.
> > I see. You must mount the catalog. In particular case you have > > registered it using "NetBeans Catalog". Mount it under Runtime: > > XML Entity Catalogs: Mount Catalog from popup. > > Now it works! > Could it be done programmatically on module installation? I most > definitely sure that it could be done, just need some guidance :-) It is not easy. Reason was that a user must decide on his own what catalogs to mount. No hidden magic. But you are right that by installing a module user already expressed his intention. But it requires module catalogs, you cannot use system wide for this purpose properly.
Target milestone was changed from not determined to TBD
*** Issue 26243 has been marked as a duplicate of this issue. ***
See issue #26243 for more detailed suggestions. One more to add: I suggest that the XML Catalogs node might be removed from the Runtime tab and placed in the Options window, i.e. UI/Services/.../XMLCatalogs.shadow -> Services/XMLCatalogs or similar. One benefit of this would be that you could use the Options window to make a particular catalog project-specific or global, etc.
The Node presents container of mounted catalogs. It would be more usefull if user (or module writer providing mounting) could define layer per mounted catalog. The Node itself is not subject of layering.
Of course I meant that for each node representing a catalog, you could decide which layer it corresponds to. This functionality is automatic if (1) the node listing catalogs is in UI/Services/ somewhere, (2) the node for a catalog has a DataObject cookie on the system filesystem.
Affects startup performance (web/advanced module register catalog for web application deployment descriptors in ModuleInstall.restored)
Introduced SFS folder Plugins/XML/UserCatalogs that can contain DataObjects featuring InstanceCookie.Of xml.catalog.spi.CatalogReader. These are added at the end of mounted catalogs list (the lowest priority) automatically. It's fixed constrain that radically simplifies the issue still not affecting user. Add dependency on: org.netbeans.modules.xml.catalog/1 > 0.9 if you wanna enjoy it. I have updated web/advanced code to test it.
Just curious - are you now also storing user-mounted catalogs consistently using this folder? Or still the old way?
This functionality is targeted to be a part of NetBeans 3.5 standard release. At this moment it is necessary to stabilize it fully, pass I18N checks, pass A11Y checks, pass UI checks and properly document it.
Very late reply to Jesse's question. Users' mounted catalogs are stored using old way, they need to be project specifics and the persistence model is a part of Catalogs SPI contract. I do not plan to change it until it becomes blocker (e.g. while porting to new projects infrastructure).
Removing #34223 blocker. It's already in prj40_prototype branch.
For projects based IDE created issue #34407.
OK
*** Issue 36194 has been marked as a duplicate of this issue. ***
Seems that this feature was never properly documented, so: committed * Up-To-Date 1.2 xml/arch/answers.xml committed * Up-To-Date 1.3 xml/catalog/src/org/netbeans/modules/xml/catalog/spi/CatalogProvider.java committed * Up-To-Date 1.4 xml/catalog/src/org/netbeans/modules/xml/catalog/spi/CatalogReader.java committed * Up-To-Date 1.3 xml/catalog/src/org/netbeans/modules/xml/catalog/spi/package.html