-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with migration to 4.2.6 #561
Comments
The warnings depend on the XML parser - looks like you might have multiple versions on the classpath. Can you check the dependency hierarchy and report on all XML related libraries shown? |
The null pointer exception seems unrelated though. Is there a value for the reasoner class name in your version of the code? |
Thank you for the answer. For the first problem I resolved deleting the pellet dependency. But now if I want to use pellet as reasoner, how should I do? |
If pellet has a dependency on xerces, it needs to be removed. Also, I On Sep 27, 2016 8:30 AM, "fedeMarra" notifications@github.com wrote:
|
@sesuncedu What is the maven repository for complexible tree? I couldn't to found this repo. |
The github organization is now named stardog-union . @evren is still named The dependency on xerces-impl is still there, so you might want to exclude On Sep 27, 2016 10:56 AM, "fedeMarra" notifications@github.com wrote:
|
Sorry, you could report me what is the right version of Pellet for owl api 4? Where should I search the repository? |
My changes for owlapi 4 were merged but the owlapi version was rolled back to 3.5.x - at least that was the case a few months ago. There is a Pellet fork called Openllet that uses owlapi 5. It is better supported than my fork (2.4.0-ignazio1977). You can find it here: http://search.maven.org/#search%7Cga%7C1%7COpenllet The reasoner name must be changed from null to the actual class name of the OWLReasonerFactory that you plan to use - this is reasoner specific. I'm sure there's a comment to that effect. |
Thank you! I resolved the nullpointException. |
It should the same way as Pellet does - with a configuration file, if I recall correctly. |
I use owl api 3.5.0 version and i would like to migrate to 4.x. I use Eclipse and for the dependency I use maven repository. For the migration I added/modified to my pom file these dependencies:
For the test i use the tutorial SimpleHierarchyExample.java. But I have different warn and error.
`[main] WARN org.semanticweb.owlapi.util.SAXParsers - http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit not supported by parser type org.apache.xerces.jaxp.SAXParserImpl
[main] WARN org.semanticweb.owlapi.util.SAXParsers - entityExpansionLimit not supported by parser type org.apache.xerces.jaxp.SAXParserImpl
[main] WARN org.semanticweb.owlapi.util.SAXParsers - http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit not supported by parser type org.apache.xerces.jaxp.SAXParserImpl
[main] WARN org.semanticweb.owlapi.util.SAXParsers - entityExpansionLimit not supported by parser type org.apache.xerces.jaxp.SAXParserImpl
Exception in thread "main" java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at KnowladgeBase.KB.SimpleHierarchyExample.main(SimpleHierarchyExample.java:115)
`
I tried different test but I can't to resolve. I do not know if I was right to migrate and I don't know if it's worth it. it's better if I stay at the 3 version?
Thanks for the help.
The text was updated successfully, but these errors were encountered: