uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Burn Lewis (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-5274) Support descriptor customization by allowing external setting variables in some fields
Date Thu, 02 Feb 2017 20:30:51 GMT

    [ https://issues.apache.org/jira/browse/UIMA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850440#comment-15850440

Burn Lewis commented on UIMA-5274:

Since the envVarRef element is actually allowed in many more places that the 4 documented,
and since these entries are processed before the external settings are loaded in produceAnalysisEngine,
the support for ${variable-name} substitution has been limited to the name & location
attributes of the import element, and to the fileUrl value for fileResourceSpecifiers.
If a referenced external setting is undefined, the value is not changed, and a warning message
names the culprit, e.g.

org.apache.uima.resource.metadata.impl.MetaDataObject_impl.resolveSettings(1674): WARNING:
org.apache.uima.resource.ResourceConfigurationException: Undefined reference to external override
variable "bug" when evaluating "analysis_${engine}/NamesAndPersonTitles_TAE.xml"

> Support descriptor customization by allowing external setting variables in some fields
> --------------------------------------------------------------------------------------
>                 Key: UIMA-5274
>                 URL: https://issues.apache.org/jira/browse/UIMA-5274
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>            Reporter: Burn Lewis
>            Assignee: Burn Lewis
>            Priority: Minor
>             Fix For: 3.0.0SDK-beta, 2.10.0SDK
> Currently the <envVarRef> element supports customization via system properties
in 4 ways (see below).  UIMA could also support the $\{variable-name} syntax in these text
fields.  In addition it could also be supported in the value for the name and location attributes
of the import element so that an aggregate's delegates could be controlled via external settings.
 This might also be done by changing the primitive descriptor as in 2 & 3 below, but in
some cases a completely different delegate descriptor is preferable.
> From the References document:
> The syntax for environment variable references is <envVarRef>[VariableName]</envVarRef>
, where [VariableName] is any valid Java system property name. Environment variable references
are valid in the following places:
> 1)   The value of a configuration parameter (String-valued parameters only)
> 2)  The <annotatorImplementationName> element of a primitive AE descriptor
> 3)   The <name> element within <analysisEngineMetaData>
> 4)   Within a <fileResourceSpecifier> or <fileLanguageResourceSpecifier>

This message was sent by Atlassian JIRA

View raw message