sszuev commented on issue #1961: URL: https://github.com/apache/jena/issues/1961#issuecomment-1646241895
In OWL-API (and ONT-API), there is a concurrent `OWLOntologyManager` in additional to the standard one (e.g. OWL-API impl: https://github.com/owlcs/owlapi/blob/version5/impl/src/main/java/uk/ac/manchester/cs/owl/owlapi/concurrent/ConcurrentOWLOntologyImpl.java) All Ontologies in a manager and manager itself use the single `ReadWriteLock` instance, so it is difficult to me to imagine a scenario with deadlocks. The same in ONT-API - RW-lock is not only about Graph operations, but also about managing references between ontologies, etc. > what is the contract for the application? Maybe "contract" is not quite the right term, sorry for the misleading. The goal of ONT-API is to support all the features of the classic OWL-API-impl, having an RDF as the basis (with arbitrary nature). Concurrent manager is used, for example, in Protege (btw I have RDF-based fork of Protege with ONTAPI inside, as an example of ONTAPI use). Not sure concurrent manager in Protege is a correct solution (there are only two thread - main & EDT. it is a swing application). Also, I raised a question https://github.com/owlcs/owlapi/issues/1110 Now we know couple of usages in ancient projects. Maybe someone will give more examples. > GraphTxn - if the Txn troubles you ignore Txn. I should take a closer look at it. Maybe it would be a new feature in ONTAPI. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
