From: Matthew H. <mat...@cs...> - 2006-04-11 14:46:11
|
All, I'd like to subclass OWLRDFParser and OWLConsumer for more control over imports. However, during importing, the OWLConsumer creates new instances of OWLRDFParser and OWLConsumer for each imported ontology - this is hard coded into OWLConsumer (see below). I'd like to make this more flexible so that reflection is used to create instances of OWLRDFParser and OWLConsumer. To remedy this, I propose that class name parameters are added to the OWLConnection parameter map for the names of the OWLRDFParser and OWLConsumer classes. Any objections? Cheers, Matthew importedOntology = onto.getOWLConnection().createOntology(obj, obj); /* Now parse it. */ OWLRDFParser parser = new OWLRDFParser(); /* Pass on my parent parser's options to the new parser */ parser.setOptions( myParser.getOptions() ); /* Create a new consumer, that shares my assumptions */ OWLConsumer consumer = new OWLConsumer( importedOntology ); |