You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2009/08/28 23:15:32 UTC

[jira] Closed: (UIMA-1531) Need a script to launch a UIMA-AS service via RunWithJarPath

     [ https://issues.apache.org/jira/browse/UIMA-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-1531.
-------------------------------

    Resolution: Fixed

> 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
>            Reporter: 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.