Project

General

Profile

Bug #15

metacat depends on Oracle parser, should be SAX

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

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

0%

Estimated time:
Bugzilla-Id:
15

Description

need to make metacata only dependant on the SAX parser, probably SAX2 for
namespace support.

History

#1 Updated by Matt Jones about 19 years ago

the current DBWriter class uses the oracle parser explicitly. See the example
in DBQuery.java to demonstarte how to use any SAX compliant parser. Still need
to configure this as a runtime parameter in the config files, but the basic
infrastructure is shown in DBQuery.

#2 Updated by Matt Jones almost 19 years ago

All of the metacat classes use the SAX2 API now for loading and parsing XML
documents. The specific parser is dynamically loaded at runtime by getting the
"saxparser" property from the metacat.properties file. This technique requires
that the appropriate jar file containing the SAX2 parser be locatable onthe
CLASSPATH or a runtime exception will occur. The only dependence on the oracle
parser left is for XSL transforms, which is treated as a seperate issue.

#3 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 15

Also available in: Atom PDF