Project

General

Profile

Bug #16

validation engine uses OASIS XML Catalog

Added by Matt Jones over 19 years ago. Updated over 17 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
metacat
Target version:
Start date:
06/08/2000
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
16

Description

need to switch the EntityResolver from the Oasis XML Catalog to the internal,
database-based entity resolver.

History

#1 Updated by Matt Jones over 19 years ago

Fixed DBValidate validation engine so that it now uses DBEntityResolver to
resolve system IDs for DTD locations when doing validation. Although it is
still possible to use the OASIS catalog system, it is no longer required, and
MetaCatServlet no longer uses it. Also, changed output of DBValidate to now
produce XML formatted errors to make it easier for applications to utilize the
information.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 16

Also available in: Atom PDF