code: private void triggerOntologyChanged() {
  		if (loadingData) {
  			return;
  		}
  		OWLModelManager owlmm = owlEditorKit.getOWLModelManager();
  		OWLOntology ontology = owlmm.getActiveOntology();
  
  		if (ontology == null) {
  			return;
  		}
  
  		OWLClass newClass = owlmm.getOWLDataFactory().getOWLClass(IRI.create("http://www.unibz.it/inf/obdaplugin#RandomClass6677841155"));
  		OWLAxiom axiom = owlmm.getOWLDataFactory().getOWLDeclarationAxiom(newClass);
  
  		try {
  			AddAxiom addChange = new AddAxiom(ontology, axiom);
  			owlmm.applyChange(addChange);
  			RemoveAxiom removeChange = new RemoveAxiom(ontology, axiom);
  			owlmm.applyChange(removeChange);
  //			owlmm.fireEvent(EventType.ACTIVE_ONTOLOGY_CHANGED);
  		} catch (Exception e) {
  			log.warn("Exception forcing an ontology change. Your OWL model might contain a new class that you need to remove manually: {}",
  					newClass.getIRI());
  			log.warn(e.getMessage());
  			log.debug(e.getMessage(), e);
  		}
  	}
docs: *
  Protege wont trigger a save action unless it detects that the OWLOntology
  currently opened has suffered a change. The OBDA plugin requires that
  protege triggers a save action also in the case when only the OBDA model
  has suffered changes. To accomplish this, this method will "fake" an
  ontology change by inserting and removing a class into the OWLModel.