[ https://issues.apache.org/jira/browse/UIMA-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein reopened UIMA-1531: --------------------------------- In the previous version of UIMA AS, the CVD application could be used to run a uima-as service via a jms-client descriptor. This doesn't work now because of missing UIMA AS jars from the CVD classpath. This is also true for other core UIMA command line scripts. One workaround could be to create an appropriate UIMA_CLASSPATH with a bunch of jars. An more user friendly workaround would be to add support for UIMA_JAR_PATH to the core UIMA command scripts. Comments? > 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.