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.
| Summary: | Publish new project schemas for E | ||
|---|---|---|---|
| Product: | usersguide | Reporter: | Jesse Glick <jglick> |
| Component: | Projects | Assignee: | Jesse Glick <jglick> |
| Status: | CLOSED FIXED | ||
| Severity: | blocker | CC: | pkuzel |
| Priority: | P2 | ||
| Version: | 4.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 51952, 57459 | ||
| Bug Blocks: | |||
|
Description
Jesse Glick
2005-01-13 16:35:34 UTC
Sorry, wrong owner. Also projectuiopenfiles/1. On related note. In IDE there is some Project Entity Catalog. It's too dumb. It requires Internet connection because its URIResolver resolves: http://www.netbeans.org/ns/project/1 to http://www.netbeans.org/ns/project/1.xsd http://www.netbeans.org/ns/nb-module-project/1 to http://www.netbeans.org/ns/nb-module-project/1.xsd instead of expected behaviour, mapping to nbres://something. It should also reasonably implement CatalogReader.getPublicIDs() method. The dumb entity resolver helped to discover issue #55615. Re. web location of schemas: see issue #42686. For now, there is no API permitting modules (e.g. project types) to register local schema locations. When there is, the entity resolver will use it, but in the meantime no. Here I meant visualization trick Web modules use. Their getPublicIDs() returns: "SCHEMA " + actual_ID. Their getSystemID() resolves these auxiliary IDs to actual schema locations. Final effect is that user can browse and view schemas from UI. Regarding schema resolution support. JDK 5.0 defines schema location resolution interfaces. Once moving toward that platform one can fit them into UserCatalog and describe optional (but recommended) contract in catalogs/spi/package.html. I have no idea what you are talking about re. "SCHEMA " + actualID but this issue is probably not the right place to discuss it. If there is something that the project system should do better, please file a separate RFE with the suggestion (and links to relevant documentation, or a patch). Re. JDK 5.0 support for schema location APIs - well we can use 5.0 APIs with a little reflection, it may be worth it. Should be filed & tracked separately I suppose. Fixed except for web/J2EE modules (see subissues). RCS file: /cvs/www/www/ns/ant-project-references/2.xsd,v done Checking in www/www/ns/ant-project-references/2.xsd; /cvs/www/www/ns/ant-project-references/2.xsd,v <-- 2.xsd initial revision: 1.1 done RCS file: /cvs/www/www/ns/j2se-project/2.xsd,v done Checking in www/www/ns/j2se-project/2.xsd; /cvs/www/www/ns/j2se-project/2.xsd,v <-- 2.xsd initial revision: 1.1 done RCS file: /cvs/www/www/ns/projectui-open-files/1.xsd,v done Checking in www/www/ns/projectui-open-files/1.xsd; /cvs/www/www/ns/projectui-open-files/1.xsd,v <-- 1.xsd initial revision: 1.1 done Verified. |