Community
Participate
Working Groups
Take the following scenario: - Add a "Next Catalog" entry to the XML catalog - Test that the entry works properly and documents are correctly resolved - Make modifications to the catalog XML file, change URIs so that documents cannot be resolved - Test resolving the catalog entries again. They will continue to work. This is because these entries have been cached. There doesn't seem to be a way to reload XML Catalog entries other than removing and adding them back. There should be an option to reload all cached entries.
Created attachment 175816 [details] patch We are using cached values , even if we remove and add NextCatalog, value cached for the first time are being used.Even though we may see new catalogs in preferences , behind the scene, only cached(stale) values are being used.I have added a ClearCache button in preferences page.
I am facing this issue, as well. In our case, an m2eclipse project configurator tries to put nextcatalog entries into the xml catalog user catalog entries. The catalog file may change as these catalog files are generated based on the xsd files in a folder. The change is not taken into account, because the Catalog caches the old referencing catalog in case of nextcatalog entries. Removing the nextcatalog entry and readding it does not solve the problem, becauase the entries from the catalog set are never removed. So next time, when the nextcatalog entry tries to "createOrLookup" the catalog from the catalog set to retrieve the referencing catalog, it will retrieve the old catalog object. In case of removing a catalog, the catalog set should also be changed. -- Vazul
Code checked in. Just tweaked Clear Cache to Reload Entries and removed some copy/paste comments.
