Describe the bug
Dear Sirs,
I am evaluating the capabilities and I am impressed by the tool. Nevertheless, I am facing an issue when designing an ontology, which is referencing other external ontologies. When creating a new graphol model from an OWL file, which is including a owl:imports statement I do not see the classes and other elements from the imported ontology in the explorer.
If I want to use the "add" button in the dialog section "Imported Ontology" within the "Ontology Manager" to declare such an "import" resp. reference statement, the system (Version 3.8 in Windows 11) ends up with an error message:
"...
Traceback (most recent call last):
File "eddy\core\jvm_init_.py", line 597, in getJavaClass
AttributeError: Java package 'com' has no attribute 'obdasystems'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "eddy\ui\import_ontology.py", line 251, in onContinueClicked
File "eddy\ui\import_ontology.py", line 156, in startImportProcess
File "eddy\core\loaders\owl2.py", line 171, in init
File "eddy\core\jvm_init_.py", line 600, in getJavaClass
eddy.core.jvm.JVMClassNotFoundError: No such class com.obdasystems.eddy.ImportListener: Java package 'com' has no attribute 'obdasystems'
..."
If I use the "Import OWL file" from the toolbar the external ontology will be fully imported and merged within the current ontology. But this behavior is not expected according to the owl:imports statement. Instead of merging the external ontology in should be used as reference only, or?
Regards
Matthias
Reproduction Steps
use the "add" button in the dialog section "Imported Ontology" within the "Ontology Manager"
Expected Result
The content of the external ontology will be presented in the explorer to become usable on the canvas. As example I want to model statements like:
"...
@Prefix myOnt: http://current.com/ontology#
@Prefix externalOnt: http://external.com/ontology#
myOnt:individual rdf:type externalOnt:class
..."
Actual Result
Traceback (most recent call last):
File "eddy\core\jvm_init_.py", line 597, in getJavaClass
AttributeError: Java package 'com' has no attribute 'obdasystems'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "eddy\ui\import_ontology.py", line 251, in onContinueClicked
File "eddy\ui\import_ontology.py", line 156, in startImportProcess
File "eddy\core\loaders\owl2.py", line 171, in init
File "eddy\core\jvm_init_.py", line 600, in getJavaClass
eddy.core.jvm.JVMClassNotFoundError: No such class com.obdasystems.eddy.ImportListener: Java package 'com' has no attribute 'obdasystems'
Affected Versions
3.8
Installation
Standalone
Operating System
Windows
Operating System Version
Windows 11
Operating System Architecture
x86_64
Log
Describe the bug
Dear Sirs,
I am evaluating the capabilities and I am impressed by the tool. Nevertheless, I am facing an issue when designing an ontology, which is referencing other external ontologies. When creating a new graphol model from an OWL file, which is including a owl:imports statement I do not see the classes and other elements from the imported ontology in the explorer.
If I want to use the "add" button in the dialog section "Imported Ontology" within the "Ontology Manager" to declare such an "import" resp. reference statement, the system (Version 3.8 in Windows 11) ends up with an error message:
"...
Traceback (most recent call last):
File "eddy\core\jvm_init_.py", line 597, in getJavaClass
AttributeError: Java package 'com' has no attribute 'obdasystems'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "eddy\ui\import_ontology.py", line 251, in onContinueClicked
File "eddy\ui\import_ontology.py", line 156, in startImportProcess
File "eddy\core\loaders\owl2.py", line 171, in init
File "eddy\core\jvm_init_.py", line 600, in getJavaClass
eddy.core.jvm.JVMClassNotFoundError: No such class com.obdasystems.eddy.ImportListener: Java package 'com' has no attribute 'obdasystems'
..."
If I use the "Import OWL file" from the toolbar the external ontology will be fully imported and merged within the current ontology. But this behavior is not expected according to the owl:imports statement. Instead of merging the external ontology in should be used as reference only, or?
Regards
Matthias
Reproduction Steps
use the "add" button in the dialog section "Imported Ontology" within the "Ontology Manager"
Expected Result
The content of the external ontology will be presented in the explorer to become usable on the canvas. As example I want to model statements like:
"...
@Prefix myOnt: http://current.com/ontology#
@Prefix externalOnt: http://external.com/ontology#
myOnt:individual rdf:type externalOnt:class
..."
Actual Result
Traceback (most recent call last):
File "eddy\core\jvm_init_.py", line 597, in getJavaClass
AttributeError: Java package 'com' has no attribute 'obdasystems'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "eddy\ui\import_ontology.py", line 251, in onContinueClicked
File "eddy\ui\import_ontology.py", line 156, in startImportProcess
File "eddy\core\loaders\owl2.py", line 171, in init
File "eddy\core\jvm_init_.py", line 600, in getJavaClass
eddy.core.jvm.JVMClassNotFoundError: No such class com.obdasystems.eddy.ImportListener: Java package 'com' has no attribute 'obdasystems'
Affected Versions
3.8
Installation
Standalone
Operating System
Windows
Operating System Version
Windows 11
Operating System Architecture
x86_64
Log