[
https://issues.apache.org/jira/browse/UIMA-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765667#action_12765667
]
Jerry Cwiklik commented on UIMA-1531:
-------------------------------------
Most of UIMA scripts in /bin repeat the same set up steps of:
- checking for UIMA_HOME
- calling setUimaClassPath
- setting UIMA_JAVA_CALL variable
- running java using exactly the same -D's
As Burn said, it would be nice to remove this redundancy and replace it with a
common script that would perform common setup steps and finally start the jvm
with common options. Existing scripts will still be used with their contents
simplified. The common script will take as arguments the class (containing the
main method) and variables required by the main program. The script will use
Bootstrap loader to load classes and jars from UIMA_CLASSPATH,UIMA_JAR_PATH,
and ACTIVEMQ_HOME.
> Need a script to launch a UIMA-AS service via RunWithJarPath
> ------------------------------------------------------------
>
> Key: UIMA-1531
> URL: https://issues.apache.org/jira/browse/UIMA-1531
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> Use existing RunWithJarPath.class from the core to enable loading jars
> dynamically when launching UIMA AS service. Currently setUimaClasspath is
> called to setup static classpath before deployment of UIMA_Service. For more
> flexibility it would be better to
> load all jar files from specified locations instead of depending on them to
> be statically defined in setUimaClasspath. One of the reasons for supporting
> dynamically loaded jars is the naming scheme used by ActiveMQ. Each version
> comes with a differently named jars like for example
> apache-activemq-4.1.1.jar, activemq-all-5.2.0.jar, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
