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: | Support URLResolvers and SchemaResolvers | ||
---|---|---|---|
Product: | xml | Reporter: | Milan Kuchtiak <mkuchtiak> |
Component: | Catalog | Assignee: | issues@xml <issues> |
Status: | NEW --- | ||
Severity: | blocker | Keywords: | API |
Priority: | P1 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | TASK | Exception Reporter: | |
Bug Depends on: | 27930 | ||
Bug Blocks: | 26477, 26878 |
Description
Milan Kuchtiak
2002-08-28 10:47:45 UTC
It depends o JSR-63. Otherwise we need to be parser specifics. We should upgrade to new Apache's xml-commons resolver library that supports URIResolvers. At the same time we need to extend ...xml.catalog.api specification by mentioning that CatalogReader may optionally implement URIResolver. URIResolvers may be used for XML Schema resolution mechanism. Actualy it depends on mentioned JSR-63. Unscheduling from my todo list. New owner is gladly welcome. Meanwhile assigning to abstract issues@xml.netbeans.org owner. This issue should have priority P1 since it blocks issue #26477 of P1 priority Milan, is it still a valid use-case? If no, please mark it as INVALID. If yes, can you explain the requirement in details and give me some examples. |