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.

Bug 22848 - Module writers can add XML catalog using layer.xml files.
Summary: Module writers can add XML catalog using layer.xml files.
Alias: None
Product: xml
Classification: Unclassified
Component: Catalog (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: issues@xml
: 26243 36194 (view as bug list)
Depends on:
Blocks: 27720 26004 29473 33232
  Show dependency tree
Reported: 2002-04-26 10:36 UTC by Milan Kuchtiak
Modified: 2007-09-25 01:30 UTC (History)
5 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kuchtiak 2002-04-26 10:36:55 UTC
This is desirable mainly for adding DTD references in order 
to provide xml files with code completion.
Comment 1 _ pkuzel 2002-06-03 12:19:28 UTC
> > 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.
Comment 2 Marek Grummich 2002-07-19 16:18:34 UTC
Target milestone was changed from not determined to TBD
Comment 3 Jesse Glick 2002-08-12 16:12:01 UTC
*** Issue 26243 has been marked as a duplicate of this issue. ***
Comment 4 Jesse Glick 2002-08-12 16:15:23 UTC
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.
Comment 5 _ pkuzel 2002-08-12 17:30:41 UTC
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. 
Comment 6 Jesse Glick 2002-08-12 20:44:06 UTC
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.
Comment 7 _ rkubacki 2002-12-10 15:55:57 UTC
Affects startup performance (web/advanced module register catalog for
web application deployment descriptors in ModuleInstall.restored)
Comment 8 _ pkuzel 2002-12-17 15:02:54 UTC
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.
Comment 9 Jesse Glick 2002-12-17 15:28:02 UTC
Just curious - are you now also storing user-mounted catalogs
consistently using this folder? Or still the old way?
Comment 10 _ pkuzel 2003-02-06 10:38:32 UTC
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.
Comment 11 _ pkuzel 2003-04-24 18:10:31 UTC
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). 
Comment 12 _ pkuzel 2003-06-16 13:15:20 UTC
Removing #34223 blocker. It's already in prj40_prototype branch.
Comment 13 _ pkuzel 2003-06-16 13:32:58 UTC
For projects based IDE created issue #34407.
Comment 14 dmladek 2004-08-20 08:58:09 UTC
Comment 15 Jesse Glick 2005-01-13 19:17:23 UTC
*** Issue 36194 has been marked as a duplicate of this issue. ***
Comment 16 Jesse Glick 2005-01-13 21:09:45 UTC
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        
committed   * Up-To-Date  1.4        
committed   * Up-To-Date  1.3