[
https://issues.apache.org/jira/browse/UIMA-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilo Goetz closed UIMA-487.
----------------------------
Resolution: Won't Fix
We need to trust users to set up their classpaths correctly. We can't guard
against users polluting their classpaths with conflicting libraries.
> XCAS operations may slow down when using command line tools
> -----------------------------------------------------------
>
> Key: UIMA-487
> URL: https://issues.apache.org/jira/browse/UIMA-487
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 2.1, 2.2
> Environment: Windows, command line tools in 'bin' folder
> Reporter: Lev Kozakov
>
> Problem description:
> I run documentAnalyzer tool from command line in Win to process 500KB text
> file by using a sample AE, create XMI output and view it in the built-in Java
> Viewer. The tool takes about 25 sec to open the output XMI file in the
> viewer. For bigger files this time may increase significantly. This happens
> only in those Win machines, where WebSphere products are installed.
> Problem analysis:
> The setUimaClassPath.bat script creates UIMA_CLASSPATH by adding UIMA
> resources to the default system CLASSPATH, which may already include 3rd
> party JARs (like eglbatchgen.jar in WebSphere products) containing their own
> implementation of org.xml.sax packages. Such JAR files may conflict with
> standard JDK runtime JARs and slow down XCAS related operations. If I
> manually modify the documentAnalyzer.bat script to use 'clear' UIMA
> CLASSPATH, w/o default system CLASSPATH, my XMI file opens reasonably fast (<
> 2 sec).
> Possible suggestions:
> a) not using default system CLASSPATH in the UIMA_CLASSPATH;
> b) create a tool that can identify possible CLASSPATH conflicts and form
> UIMA_CLASSPATH accordingly.
> -- Lev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
