Triggering an update of the cached edges in OWLGraphWrapper

From TheITGuy...@gmail.com on February 06, 2013 06:13:25

Additions/removal of OWLSubClassOfAxiom in an ontology are not seen by the OWLGraphWrapper container. Might be nice to add a method to trigger an update of the cached edges.

Example:

OWLSubClassOfAxiom ax = factory.getOWLSubClassOfAxiom(myOWLClass1, myOWLClass2);
AddAxiom addAx = new AddAxiom(myWrapper.getSourceOntology(), ax);
myWrapper.getManager().applyChange(addAx);
for (OWLGraphEdge edge: myWrapper.getCompleteEdgesBetween(myClass, myClass2)) {
System.out.println(edge);//no edges found here
}
//force an update, but throw checked Exceptions, and looks like a hack.
myWrapper = new OWLGraphWrapper(myWrapper.getSourceOntology());
for (OWLGraphEdge edge: myWrapper.getCompleteEdgesBetween(myClass, myClass2)) {
System.out.println(edge);//the edge is correctly displayed
}

Original issue: http://code.google.com/p/owltools/issues/detail?id=49

Start with OWLGraphWrapper, especially getCompleteEdgesBetween and the source-ontology change flow shown in the example. Reproduce the AddAxiom case and trace why the cached edges remain unchanged; done means a supported update path makes the newly added subclass edge visible without reconstructing the wrapper.