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 53364 - Publish new project schemas for E
Summary: Publish new project schemas for E
Status: CLOSED FIXED
Alias: None
Product: usersguide
Classification: Unclassified
Component: Projects (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on: 51952 57459
Blocks:
  Show dependency tree
 
Reported: 2005-01-13 16:35 UTC by Jesse Glick
Modified: 2006-03-24 13:05 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2005-01-13 16:35:34 UTC
j2seproject/2, artifact/2, and perhaps freeform/2
schemas should be published before the release of 4.1.
Comment 1 Jesse Glick 2005-01-13 16:36:00 UTC
Sorry, wrong owner.
Comment 2 Jesse Glick 2005-01-13 18:46:39 UTC
Also projectuiopenfiles/1.
Comment 3 _ pkuzel 2005-02-28 15:40:14 UTC
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.
Comment 4 _ pkuzel 2005-02-28 15:52:11 UTC
The dumb entity resolver helped to discover issue #55615.
Comment 5 Jesse Glick 2005-03-07 16:54:10 UTC
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.
Comment 6 _ pkuzel 2005-03-10 10:09:53 UTC
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.
Comment 7 Jesse Glick 2005-04-04 23:58:53 UTC
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.
Comment 8 Jesse Glick 2005-04-05 00:18:46 UTC
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
Comment 9 Jaromir Uhrik 2005-07-14 16:20:20 UTC
Verified.