You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2014/11/03 23:35:34 UTC
[jira] [Commented] (UIMA-4075) External Resources extension
[ https://issues.apache.org/jira/browse/UIMA-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195247#comment-14195247 ]
Marshall Schor commented on UIMA-4075:
--------------------------------------
External Resources are defined in the <resourceManagerConfiguration> element.
See: http://uima.apache.org/d/uimaj-2.6.0/references.html#ugr.ref.xml.component_descriptor.aes.primitive and scroll down to section 2.4.1.9
Part of the configuration for this is the "Resource Specifier". The documentation discusses 3 alternatives for this, including a "customResourceSpecifier", which in turn is described here: http://uima.apache.org/d/uimaj-2.6.0/references.html#ugr.ref.xml.component_descriptor.custom_resource_specifiers
Custom Resource Specifiers may provide what you're looking for; they include a <parameters> element which has key-value pairs.
Would this work for what you want?
> External Resources extension
> ----------------------------
>
> Key: UIMA-4075
> URL: https://issues.apache.org/jira/browse/UIMA-4075
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework, Eclipse plugins
> Affects Versions: 2.6.0SDK
> Reporter: Silvestre Losada
> Labels: UIMA, configuration, external-resources
> Fix For: 2.6.1SDK
>
>
> UIMA offer a solution in order to access to external resources. Now a resource is initialized at startup time by reading external data from a file or via a URL. An external resource could be also example a database connection, database connection is composed by several parameters.
> It would be nice if the external resource could hold a list of pairs <key-value> in order to offer more flexibility configuring external resources. The configuration parameters should be specified in descriptor file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)