[ 
https://issues.apache.org/jira/browse/CTAKES-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923029#comment-15923029
 ] 

James Joseph Masanz commented on CTAKES-363:
--------------------------------------------

in org.apache.ctakes.core.resource.FileResourceImpl, an attempt is made to 
create a File, however if running from binary, the uri refers to a file within 
a jar, so a File cannot be created
The code fragment is: new File(dr.getUri())
The URI's string value is:
jar:file:/CTAKES_HOME/lib/ctakes-smoking-status-res-3.2.2.jar!/org/apache/ctakes/smokingstatus/analysis_engine/ProductionPostSentenceAggregate_step1.xml



> The smoking pipeline gives a URI is not hierarchical error
> ----------------------------------------------------------
>
>                 Key: CTAKES-363
>                 URL: https://issues.apache.org/jira/browse/CTAKES-363
>             Project: cTAKES
>          Issue Type: Bug
>          Components: ctakes-smoking-status
>    Affects Versions: 3.2.1, 3.2.2
>         Environment: I have version 3.2.2 installed in both on a Windows and 
> a Mac system.
>            Reporter: Harshad
>
> I am trying to use the Smoking Pipeline using the User version (3.2.2).
> The following is the configuration I use:
> Descriptor: ../apache-ctakes-3.1.1/desc/ctakes-
> core/desc/collection_reader/FilesInDirectoryCollectionReader.xml
> Input Directory: an input folder with test data
> Analysis Engines: SimulatedProdSmokingTAE.xml 
> (in the ctakes-smoking-status folder)
> CAS Consumers: FIleWriterCasConsumer.xml
> This worked perfectly in v3.1.1 but now it is giving me an error : 
> 'org.apache.uima.resource.ResourceInitializationException:Initialization 
> of CAS processor with name "SimulatedProdAggregateTAE" failed.
> CausedBy: 
> org.apache.uima.resource.ResourceConfigurationException:Initialization
> of CAS Processor with name "SimulatedProdAggregateTAE" failed.
> CausedBy: java.lang.IllegalArgumentException: URI is not hierarchical'



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to