I'm trying to use two OWLDB databases to manage my ontologies. They both refer to the same classes, but each contains a specific type of axioms. Currently, this is what I'm doing:
I'm not entirely sure this is a bug in owldb, hibernate or if it's an error on my code (or even an error on the .owl file, but since the ontology was successfully imported into the database I don't think it can be a problem of that kind).
Could this be caused by accessing two different ontologies at the same time?
Can you think of any hint that can help me solve this issue?
Thank you very much.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We noticed this problem in a project as well but could not track it down. It seems to be related to how the owlapi classes work which seems to conflict somehow with Hibernate.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
I'm trying to use two OWLDB databases to manage my ontologies. They both refer to the same classes, but each contains a specific type of axioms. Currently, this is what I'm doing:
This class results in this error:
I'm not entirely sure this is a bug in owldb, hibernate or if it's an error on my code (or even an error on the .owl file, but since the ontology was successfully imported into the database I don't think it can be a problem of that kind).
Could this be caused by accessing two different ontologies at the same time?
Can you think of any hint that can help me solve this issue?
Thank you very much.
We noticed this problem in a project as well but could not track it down. It seems to be related to how the owlapi classes work which seems to conflict somehow with Hibernate.