[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jwt-dev] Using OWLAPI from within the handler of a plugin menu command
- From: Florian Lautenbacher <lautenbacher@xxxxxxxxxx>
- Date: Tue, 07 Jun 2011 20:42:15 +0200
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:22.214.171.124pre) Gecko/20100624 Spicebird/0.8
it seems to me that you missed to include the OWL API library file in
the plugin definition. When the compiler tells you a
ClassNotFoundException, then the path to the library is unknown. In the
plugin.xml or MANIFEST.MF(which both opens the same dialog) you can find
the libraries that should be taken into account during build. Add the
OWLAPI.lib file (or the whole path) there and it should work.
Please have a look into the same files in the Sempa-repositories which
you probably should have already access to.
Good luck and best regards,
On 07.06.2011 18:18, Ahmed Samir Saleh Wafa wrote:
Has anyone managed to load an Ontology or generally using the OWLAPI from within the handler of a plugin menu COMMAND. I can do that from a normal class with a main method but I face an exception when I try doing it from within the execute method of the command handler. The exception is a class not found exception and it doesn't make sense because I use the same code on another NORMAL class (with a main method) in the same package of the same plugin project and it works perfectly. I was wondering if anyone has ever faced something like that ?? will appreciate any suggestions.
Thanks in advance,
jwt-dev mailing list