Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
Received-SPF: pass (nike.apache.org: domain of gcaug-uima-user@m.gmane.org
 designates 80.91.229.3 as permitted sender)
To: user@uima.apache.org
From: Jens Grivolla <j+asf@grivolla.net>
Subject: ConceptMapper: tokenizer doesn't get PEAR classpath
Date: Fri, 02 Mar 2012 17:03:57 +0100
Lines: 24
Message-ID: <jiqr1d$o1n$1@dough.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.24) Gecko/20111108 Lightning/1.0b2 Thunderbird/3.1.16

Hi,

when using the ConceptMapper from addons as a PEAR we are having 
classpath problems.  The ConceptMapper launches a tokenizer AE using its 
XML descriptor, but at that point the classpath set from the PEAR does 
not get used.

This means that it is impossible to point to a tokenizer packaged 
together with the CM based AE, or it is at least necessary to add the 
tokenizer classes (or jar) as well as all of its dependencies to the 
global classpath.

It all seems to come down to (AnnotatorAdapter.java:97):
ae = UIMAFramework.produceAnalysisEngine(aeSpecifier);

But I don't see why the classpath that is used by the ConceptMapper 
would not apply here. It must have to do with how the classpath is 
adjusted "locally" for PEARs instead of being global to the whole JVM, 
but I haven't been able to figure it out yet.

Any ideas?

Thanks,
Jens