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 Wed, 08 Feb 2017 14:28:42 GMT

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

Burn Lewis commented on UIMA-5274:
----------------------------------

Fixed problem of not clearing context.  Changed all cases to save & restore the previous
value as in some applications annotators create and run separate pipelines.  Added Junit test
of a nested AE.

> 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: Marshall Schor
>            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
(v6.3.15#6346)

Mime
View raw message