Hi Debbie,
I do not use eclipse, I won't be of any help regarding maven and eclipse
interoperability. The simplest thing is probably to download extJWNL
from http://sourceforge.net/projects/extjwnl/files/ and add all jars
under the lib/ directory in your project. Once it is done, you should be
able to load the dictionary with the following line of code:
Dictionary dictionary = Dictionary.getDefaultResourceInstance();
Let me know if it helps,
Alexandre
On 14-05-02 08:47 PM, Debbie Zhang wrote:
Thanks Alexandre for your reply!
I will try extJWNL as suggested. As I have never used maven, may I ask which
maven Eclipse plugin you use?
Thanks again for your help!
Regards,
Debbie
-----Original Message-----
From: Alexandre Patry [mailto:[email protected]]
Sent: Saturday, 3 May 2014 12:13 AM
To: [email protected]
Subject: Re: RandomAccessFile problem in UIMA
Hi Debbie,
I recommend you to use extJWNL (https://github.com/extjwnl/extjwnl)
instead of JWNL. We made the switch from JWNL and never looked back.
For your path problems, extJWNL distribute WordNet dictionaries as
maven dependencies. It should become a non-issue.
Hope this help,
Alexandre
On 02/05/2014 03:36, Debbie Zhang wrote:
Hi,
I am having problems to use JWNL wordnet in UIMA.
JWNL uses RandomAccessFile to read wordnet dictionary files. In order
to create a PEAR file, wordnet dictionary files are put in
resources/wordnet folder under project. As resources is in my Build
Path, I have no problem to run the application I created in Eclipse.
Therefore, I am certain the dictionary files can be read. However,
when I use UIMA Document Analyzer or UIMA CAS Visual Debugger to run
the annotation, I get the following error:
java.io.FileNotFoundException: resources/wordnet/data.noun (No such
file or
directory)
The error comes from the following code:
RandomAccess _file = new RandomAccessFile(path, _permissions);
I use the following code to check the current working directory of
the
class:
URL location =
PrincetonRandomAccessDictionaryFile.class.getProtectionDomain().getCod
eSourc
e().getLocation();
System.out.println(location.getFile());
It seems both situation have the same location: /project/bin/
Did anyone encounter a similar problem before? Any suggestion is
welcome.
Thank you!
Regards,
Debbie
--
Alexandre Patry, Ph.D
Chercheur / Researcher
http://KeaText.com
--
Alexandre Patry, Ph.D
Chercheur / Researcher
http://KeaText.com
